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 2/2] perf, tools: Add documentation for perf user event parameters
Date: Wed, 12 Oct 2016 14:02:07 -0700 [thread overview]
Message-ID: <1476306127-19721-2-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1476306127-19721-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
There was no proper documention for the user parameters for
events that the perf parser implements. Document them all
in the perf list manpage.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
tools/perf/Documentation/perf-list.txt | 42 ++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/tools/perf/Documentation/perf-list.txt b/tools/perf/Documentation/perf-list.txt
index 41857cce5e86..511adc684148 100644
--- a/tools/perf/Documentation/perf-list.txt
+++ b/tools/perf/Documentation/perf-list.txt
@@ -119,6 +119,48 @@ be specified as
perf stat -e cpu/event=0xa8,umask=0x1,name=LSD.UOPS_CYCLES,cmask=1/ ...
+EVENT PARAMETERS
+----------------
+
+The pmu// syntax in perf uses parameters to configure the event for the
+PMU.
+
+For a list of available parameters for each PMU please use
+
+ ls /sys/devices/*/format
+
+Common parameters are
+
+. event=NUM: Event code
+. umask=NUM: Event umask
+
+In addition perf supports some extra parameters to further configure then
+event
+
+. name=name: Use name to display the event in perf
+. period=NUM: Use sampling period NUM for the event. Similar to the -c parameter,
+but only applies to this event. Only valid for perf record and top.
+. freq=NUM: Use sampling frequency NUM for the event. Similar to the -c parameter,
+but only applies to this event. Only valid for perf record and top.
+. branch_type=TYPE: Enable last branch sampling for event. TYPE is the same
+as the argument to perf record's -j option. Use any to be equivalent to -b.
+when no is specified branch sampling is disabled for this event. Only valid
+for perf record and top.
+. time=NUM: When NUM is non zero collect a time stamp for the event.
+. call-graph=type: Enable call graph mode for the event. When no is specified call
+graph is disabled. The parameters are the as to the --call-graph option of
+perf record. Only valid for perf record and top.
+. stack-size=BYTES: For dwarf unwinding call graph mode limit the number of stack
+bytes collected to BYTES.
+. max-stack=NUM: For call graph mode limit the number of entries to NUM.
+. inherit: Inherit the event to child processes.
+. no-inherit: Do not inherit the event to child processes.
+. overwrite: Enable overwrite mode in the perf buffer.
+. no-overwrite: Do not enable overwrite mode in the perf buffer.
+. config=NUM: Configure config parameter in perf event attribute.
+. config1=NUM: Configure config1 parameter in perf event attribute.
+. config2=NUM: Configure config2 parameter in perf event attribute.
+
PER SOCKET PMUS
---------------
--
2.5.5
next prev parent reply other threads:[~2016-10-12 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 21:02 [PATCH 1/2] perf, tools: Implement branch_type event parameter Andi Kleen
2016-10-12 21:02 ` Andi Kleen [this message]
2016-10-13 11:33 ` [PATCH 2/2] perf, tools: Add documentation for perf user event parameters Jiri Olsa
2016-10-13 11:32 ` [PATCH 1/2] perf, tools: Implement branch_type event parameter Jiri Olsa
2016-10-24 18:56 ` [tip:perf/core] perf " tip-bot for Andi Kleen
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=1476306127-19721-2-git-send-email-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