mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: acme@kernel.org
Cc: jolsa@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: [PATCH] perf, tools: Describe uncore event changes in perf list
Date: Thu, 20 Apr 2017 13:54:47 -0700	[thread overview]
Message-ID: <20170420205447.25936-1-andi@firstfloor.org> (raw)

From: Andi Kleen <ak@linux.intel.com>

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

Also fix a typo in an existing example.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 tools/perf/Documentation/perf-list.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt
index f709de54707b..b6eaa2b34921 100644
--- a/tools/perf/Documentation/perf-list.txt
+++ b/tools/perf/Documentation/perf-list.txt
@@ -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
-- 
2.9.3

                 reply	other threads:[~2017-04-20 20:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170420205447.25936-1-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome