From: Andi Kleen <andi@firstfloor.org>
To: acme@infradead.org
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
masami.hiramatsu.pt@hitachi.com
Subject: [PATCH 2/2] perf, tools, probe: Clarify x86 register naming for perf probe
Date: Fri, 28 Feb 2014 06:02:15 -0800 [thread overview]
Message-ID: <1393596135-4227-3-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1393596135-4227-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Clarify how to specify x86 registers in perf probe. I recently
ran into this problem and had to figure it out from the source.
Cc: masami.hiramatsu.pt@hitachi.com
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
tools/perf/Documentation/perf-probe.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/Documentation/perf-probe.txt b/tools/perf/Documentation/perf-probe.txt
index b715cb7..1513935 100644
--- a/tools/perf/Documentation/perf-probe.txt
+++ b/tools/perf/Documentation/perf-probe.txt
@@ -136,6 +136,8 @@ Each probe argument follows below syntax.
'NAME' specifies the name of this argument (optional). You can use the name of local variable, local data structure member (e.g. var->field, var.field2), local array with fixed index (e.g. array[1], var->array[0], var->pointer[2]), or kprobe-tracer argument format (e.g. $retval, %ax, etc). Note that the name of this argument will be set as the last member name if you specify a local data structure member (e.g. field2 for 'var->field1.field2'.)
'TYPE' casts the type of this argument (optional). If omitted, perf probe automatically set the type based on debuginfo. You can specify 'string' type only for the local variable or structure member which is an array of or a pointer to 'char' or 'unsigned char' type.
+On x86 systems %REG is always the short form of the register: for example %AX. %RAX or %EAX is not valid.
+
LINE SYNTAX
-----------
Line range is described by following syntax.
--
1.8.5.3
next prev parent reply other threads:[~2014-02-28 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 14:02 Clarify perf man pages Andi Kleen
2014-02-28 14:02 ` [PATCH 1/2] perf, tools, mem: Clarify load-latency in documentation Andi Kleen
2014-03-18 8:28 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2014-02-28 14:02 ` Andi Kleen [this message]
2014-03-02 3:08 ` [PATCH 2/2] perf, tools, probe: Clarify x86 register naming for perf probe Masami Hiramatsu
2014-03-18 8:29 ` [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=1393596135-4227-3-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
/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