Skip to contentSkip to conversation

perf, tools: Describe uncore event changes in perf list

PATCH New Andi Kleen 1 participant 1 message Apr 20, 2017 perf events

lore
Share & tools
lore

Andi Kleen

author
#0 lore raw

PATCH 1/1 perf, tools: Describe uncore event changes in perf list

From: Andi Kleen <[email protected]>

Describe the new uncore wildcard PMU match in the perf list manpage.

Also fix a typo in an existing example.

---
 tools/perf/Documentation/perf-list.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)
tools/perf/Documentation/perf-list.txt +11 -1
index f709de54707b..b6eaa2b34921 100644
@@ -134,12 +134,22 @@ all the CPUs in the same socket.
 This example measures memory bandwidth every second
 on the first memory controller on socket 0 of a Intel Xeon system
 
-  perf stat -C 0 -a uncore_imc_0/cas_count_read/,uncore_imc_0/cas_count_write/ -I 1000 ...
+  perf stat -C 0 -e uncore_imc_0/cas_count_read/,uncore_imc_0/cas_count_write/ -I 1000 ...
 
 Each memory controller has its own PMU.  Measuring the complete system
 bandwidth would require specifying all imc PMUs (see perf list output),
 and adding the values together.
 
+perf supports wildcard matches on uncore PMUs. All "imc" boxes can be
+specified with
+
+  perf stat ... -e uncore_imc/cas_count_read/ -I 1000
+
+and perf will automatically measure all "imc" PMUs and sum them together.
+For the special case of a uncore prefix this can be also shortened to
+
+  perf stat ... -e imc/cas_count_read/ -I 1000
+
 This example measures the combined core power every second
 
   perf stat -I 1000 -e power/energy-cores/  -a
Signature · 1 line
2.9.3