blob: 2de34075f6a49dd443929bc9408f8887fb66812b [file] [log] [blame]
Masami Hiramatsu595c3642009-10-16 20:08:27 -04001perf-probe(1)
2=============
3
4NAME
5----
6perf-probe - Define new dynamic tracepoints
7
8SYNOPSIS
9--------
10[verse]
Masami Hiramatsuc937fe22009-12-08 17:03:30 -050011'perf probe' [options] --add='PROBE' [...]
Masami Hiramatsuc43f9d12009-11-03 19:12:13 -050012or
Masami Hiramatsuc937fe22009-12-08 17:03:30 -050013'perf probe' [options] PROBE
14or
15'perf probe' [options] --del='[GROUP:]EVENT' [...]
16or
17'perf probe' --list
Masami Hiramatsu631c9de2010-01-06 09:45:34 -050018or
19'perf probe' --line='FUNC[:RLN[+NUM|:RLN2]]|SRC:ALN[+NUM|:ALN2]'
Masami Hiramatsu595c3642009-10-16 20:08:27 -040020
21DESCRIPTION
22-----------
23This command defines dynamic tracepoint events, by symbol and registers
24without debuginfo, or by C expressions (C line numbers, C function names,
25and C local variables) with debuginfo.
26
27
28OPTIONS
29-------
30-k::
Masami Hiramatsuc43f9d12009-11-03 19:12:13 -050031--vmlinux=PATH::
Masami Hiramatsu595c3642009-10-16 20:08:27 -040032 Specify vmlinux path which has debuginfo (Dwarf binary).
33
34-v::
35--verbose::
36 Be more verbose (show parsed arguments, etc).
37
Masami Hiramatsuc43f9d12009-11-03 19:12:13 -050038-a::
Masami Hiramatsuc937fe22009-12-08 17:03:30 -050039--add=::
40 Define a probe event (see PROBE SYNTAX for detail).
41
42-d::
43--del=::
44 Delete a probe event.
45
46-l::
47--list::
48 List up current probe events.
Masami Hiramatsu595c3642009-10-16 20:08:27 -040049
Masami Hiramatsu631c9de2010-01-06 09:45:34 -050050-L::
51--line=::
52 Show source code lines which can be probed. This needs an argument
53 which specifies a range of the source code.
54
Masami Hiramatsu595c3642009-10-16 20:08:27 -040055PROBE SYNTAX
56------------
57Probe points are defined by following syntax.
58
Masami Hiramatsuaf663d72009-12-15 10:32:18 -050059 "[EVENT=]FUNC[+OFFS|:RLN|%return][@SRC]|SRC:ALN [ARG ...]"
Masami Hiramatsu595c3642009-10-16 20:08:27 -040060
Masami Hiramatsuaf663d72009-12-15 10:32:18 -050061'EVENT' specifies the name of new event, if omitted, it will be set the name of the probed function. Currently, event group name is set as 'probe'.
Masami Hiramatsuc43f9d12009-11-03 19:12:13 -050062'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.
63It 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.
Masami Hiramatsu595c3642009-10-16 20:08:27 -040064'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).
65
Masami Hiramatsu631c9de2010-01-06 09:45:34 -050066LINE SYNTAX
67-----------
68Line range is descripted by following syntax.
69
70 "FUNC[:RLN[+NUM|:RLN2]]|SRC:ALN[+NUM|:ALN2]"
71
72FUNC specifies the function name of showing lines. 'RLN' is the start line
73number from function entry line, and 'RLN2' is the end line number. As same as
74probe syntax, 'SRC' means the source file path, 'ALN' is start line number,
75and 'ALN2' is end line number in the file. It is also possible to specify how
76many lines to show by using 'NUM'.
77So, "source.c:100-120" shows lines between 100th to l20th in source.c file. And "func:10+20" shows 20 lines from 10th line of func function.
78
Masami Hiramatsu595c3642009-10-16 20:08:27 -040079SEE ALSO
80--------
81linkperf:perf-trace[1], linkperf:perf-record[1]