Lines Matching full:probe
1 perf-probe(1)
6 perf-probe - Define new dynamic tracepoints
11 'perf probe' [options] --add='PROBE' [...]
13 'perf probe' [options] PROBE
15 'perf probe' [options] --del='[GROUP:]EVENT' [...]
17 'perf probe' --list
19 'perf probe' [options] --line='LINE'
21 'perf probe' [options] --vars='PROBEPOINT'
38 Specify module name in which perf-probe searches probe points
39 or lines. If a path of module file is passed, perf-probe
40 treat it as an offline module (this means you can add a probe on
53 Define a probe event (see PROBE SYNTAX for detail).
57 Delete probe events. This accepts glob wildcards('*', '?') and character
62 List up current probe events.
71 Show available local variables at given probe point. The argument
72 syntax is same as PROBE SYNTAX, but NO ARGs.
100 Set the maximum number of probe points for an event. Default is 128.
107 In absence of -m/-x options, perf probe checks if the first argument after
108 the options is an absolute path name. If its an absolute path, perf probe
109 uses it as a target module/target user space binary to probe.
111 PROBE SYNTAX
113 Probe points are defined by following syntax.
125 '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'.
126 '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. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function.
127 It is also possible to specify a probe point by the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' is the line number and ';PTN' is the lazy matching pattern.
128 'ARG' specifies the arguments of this probe point, (see PROBE ARGUMENT).
130 PROBE ARGUMENT
132 Each probe argument follows below syntax.
137 '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.
147 probe syntax, 'SRC' means the source file path, 'ALN' is start line number,
160 This provides some sort of flexibility and robustness to probe point definitions against minor code changes. For example, actual 10th line of schedule() can be moved easily by modifying schedule(), but the same line matching 'rq=cpu_rq*' may still exist in the function.)
168 With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar".
169 With --filter "!foo* & *bar", perf probe -V shows variables which don't start with "foo" and end with "bar", like "fizzbar". But "foobar" is filtered out.
175 ./perf probe --line schedule
177 Add a probe on schedule() function 12th line with recording cpu local variable:
179 ./perf probe schedule:12 cpu
181 ./perf probe --add='schedule:12 cpu'
187 ./perf probe 'schedule;update_rq_clock*'
189 ./perf probe --add='schedule;update_rq_clock*'
193 ./perf probe --del='schedule*'
197 ./perf probe -x /bin/zsh zfree or ./perf probe /bin/zsh zfree
201 ./perf probe -x /lib/libc.so.6 malloc or ./perf probe /lib/libc.so.6 malloc
