(2014/02/28 23:02), Andi Kleen wrote: > From: Andi Kleen <a...@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...@hitachi.com > Signed-off-by: Andi Kleen <a...@linux.intel.com>
Acked-by: Masami Hiramatsu <masami.hiramatsu...@hitachi.com> Thanks! > --- > 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. > -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu...@hitachi.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/