Lines Matching refs:probe

10 this is based on kprobes (kprobe and kretprobe). So it can probe wherever
11 kprobes can probe (this means, all functions body except for __kprobes
18 current_tracer. Instead of that, add probe points via
25   p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS]	: Set a probe
26   r[:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS]		: Set a return probe
27   -:[GRP/]EVENT						: Clear a probe
33  SYM[+offs]	: Symbol+offset where the probe is inserted.
34  MEMADDR	: Address where the probe is inserted.
36  FETCHARGS	: Arguments. Each probe can have up to 128 args.
49   (*) only for return probe.
68  Per-probe event filtering feature allows you to set different filter on each
69 probe and gives you what arguments will be shown in trace buffer. If an event
75   You can enable/disable the probe by writing 1 or 0 on it.
78   This shows the format of this probe event.
84   This shows the id of this probe event.
89  You can check the total number of probe hits and probe miss-hits via
91  The first column is event name, the second is the number of probe hits,
92 the third is the number of probe miss-hits.
97 To add a probe as a new event, write a new definition to kprobe_events
105 the ABI, please try to use probe subcommand of perf-tools (you can find it
140  This clears all probe points.
146  This clears probe points selectively.