2009-10-16 18:08:27 -06:00
perf-probe(1)
=============
NAME
----
perf-probe - Define new dynamic tracepoints
SYNOPSIS
--------
[verse]
2009-12-08 15:03:30 -07:00
'perf probe' [options] --add='PROBE' [...]
2009-11-03 17:12:13 -07:00
or
2009-12-08 15:03:30 -07:00
'perf probe' [options] PROBE
or
'perf probe' [options] --del='[GROUP:]EVENT' [...]
or
'perf probe' --list
2009-10-16 18:08:27 -06:00
DESCRIPTION
-----------
This command defines dynamic tracepoint events, by symbol and registers
without debuginfo, or by C expressions (C line numbers, C function names,
and C local variables) with debuginfo.
OPTIONS
-------
-k::
2009-11-03 17:12:13 -07:00
--vmlinux=PATH::
2009-10-16 18:08:27 -06:00
Specify vmlinux path which has debuginfo (Dwarf binary).
-v::
--verbose::
Be more verbose (show parsed arguments, etc).
2009-11-03 17:12:13 -07:00
-a::
2009-12-08 15:03:30 -07:00
--add=::
Define a probe event (see PROBE SYNTAX for detail).
-d::
--del=::
Delete a probe event.
-l::
--list::
List up current probe events.
2009-10-16 18:08:27 -06:00
PROBE SYNTAX
------------
Probe points are defined by following syntax.
2009-11-03 17:12:13 -07:00
"FUNC[+OFFS|:RLN|%return][@SRC]|SRC:ALN [ARG ...]"
2009-10-16 18:08:27 -06:00
2009-11-03 17:12:13 -07:00
'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, 'RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. In addition, 'SRC' specifies a source file which has that function.
It is also possible to specify a probe point by the source line number by using 'SRC:ALN' syntax, where 'SRC' is the source file path and 'ALN' is the line number.
2009-10-16 18:08:27 -06:00
'ARG' specifies the arguments of this probe point. You can use the name of local variable, or kprobe-tracer argument format (e.g. $retval, %ax, etc).
SEE ALSO
--------
linkperf:perf-trace[1], linkperf:perf-record[1]