Lines Matching refs:which

38 	Specify vmlinux path which has debuginfo (Dwarf binary).
44 	Specify module name in which perf-probe searches probe points
47         a module which has not been loaded yet).
81 	Show source code lines which can be probed. This needs an argument
82 	which specifies a range of the source code. (see LINE SYNTAX for detail)
95 	which do not have instances are ignored.
125 	(With --add) Cache the probes. Any events which successfully added
176 …f the probe point definition.  In addition, '@SRC' specifies a source file which has that function.
179 'SDTEVENT' and 'PROVIDER' is the pre-defined event name which is defined by user SDT (Statically De…
180 Note that before using the SDT event, the target binary (on which SDT events are defined) must be s…
192 …$vars' is expanded to the local variables (including function parameters) which can access at give…
199 …which fetches a "null-terminated" string from kernel space. This means it will fail and store NULL…
200 Bitfield is another special type, which takes 3 parameters, bit-width, bit-offset, and container-si…
233  With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar".
234 …With --filter "!foo* & *bar", perf probe -V shows variables which don't start with "foo" and end w…
238 Display which lines in schedule() can be probed:
248 Add one or more probes which has the name start with "schedule".
254 Add probes on lines in schedule() function which calls update_rq_clock().