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 except those with
19 current_tracer. Instead of that, add probe points via
28   p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS]	: Set a probe
29   r[MAXACTIVE][:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS]	: Set a return probe
30   -:[GRP/]EVENT						: Clear a probe
36  SYM[+offs]	: Symbol+offset where the probe is inserted.
37  MEMADDR	: Address where the probe is inserted.
42  FETCHARGS	: Arguments. Each probe can have up to 128 args.
56   (*) only for return probe.
80 Per-probe event filtering feature allows you to set different filter on each
81 probe and gives you what arguments will be shown in trace buffer. If an event
87   You can enable/disable the probe by writing 1 or 0 on it.
90   This shows the format of this probe event.
96   This shows the id of this probe event.
104 You can check the total number of probe hits and probe miss-hits via
106 The first column is event name, the second is the number of probe hits,
107 the third is the number of probe miss-hits.
112 To add a probe as a new event, write a new definition to kprobe_events
120 the ABI, please try to use probe subcommand of perf-tools (you can find it
158 This clears all probe points.
165 This clears probe points selectively.