Skip to content

Commit a7659be

Browse files
committed
Update FAQ.md
1 parent 353a1e7 commit a7659be

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

doc/FAQ.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,3 +86,10 @@ Not all AWS instances allow users to collect CPU telemetry by exposing PMU to th
8686
* Bare metal instances: allow collection of CPU metrics from both core (e.g. instructions per cycle, cache misses) and uncore (e.g. memory controller, UPI)
8787
* Full-socket (single socket, two socket, etc) virtualized instances: e.g. m5d.12xlarge, m5.24xlarge, m5.12xlarge. Only core CPU metrics are exposed, and certain CPU performance events are forbidden (e.g. offcore response events, events collecting “any_thread” information). “arch_perfmon” flag in /proc/cpuinfo indicates if the core CPU metrics are exposed (example: https://instaguide.io/info.html?type=m5.12xlarge ). The mechanism of PMU virtualization is commonly known as vPMU.
8888

89+
## Q12
90+
91+
pcm-pcie reports that the CPU is not supported: "Jaketown, Ivytown, Haswell, Broadwell-DE, Skylake, Icelake, Snowridge and Sapphirerapids Server CPU is required for this tool! Program aborted"
92+
Can you add support for pcm-pcie for my CPU?
93+
94+
Answer: most likely you have a client CPU which does not have required hardware performance monitoring units. pcm-pcie can not work without them.
95+

0 commit comments

Comments
 (0)