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
31 p[:[GRP/][EVENT]] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe
32 r[MAXACTIVE][:[GRP/][EVENT]] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe
33 p[:[GRP/][EVENT]] [MOD:]SYM[+0]%return [FETCHARGS] : Set a return probe
34 -:[GRP/][EVENT] : Clear a probe
40 SYM[+offs] : Symbol+offset where the probe is inserted.
42 MEMADDR : Address where the probe is inserted.
47 FETCHARGS : Arguments. Each probe can have up to 128 args.
65 (\*1) only for the probe on function entry (offs == 0). Note, this argument access
68 (\*2) only for return probe. Note that this is also best effort. Depending on the
152 Per-probe event filtering feature allows you to set different filter on each
153 probe and gives you what arguments will be shown in trace buffer. If an event
159 You can enable/disable the probe by writing 1 or 0 on it.
162 This shows the format of this probe event.
168 This shows the id of this probe event.
176 You can check the total number of probe hits and probe miss-hits via
178 The first column is event name, the second is the number of probe hits,
179 the third is the number of probe miss-hits.
186 The difference is that the probe definition parameters are comma-delimited
198 To add a probe as a new event, write a new definition to kprobe_events
206 the ABI, please try to use probe subcommand of perf-tools (you can find it
244 This clears all probe points.
251 This clears probe points selectively.