Skip to content

Commit 03cfa4c

Browse files
authored
fix formatting
1 parent 37a4c1e commit 03cfa4c

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

doc/FAQ.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,5 @@ Is PCM supported on AWS instances
8484
Not all AWS instances allow users to collect CPU telemetry by exposing PMU to the user. The following instances can be used:
8585

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)
87-
Full-socket (single socket, two socket, etc)
88-
* 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.
87+
* 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.
8988

0 commit comments

Comments
 (0)