Lines Matching full:event

2 Kprobe-based Event Tracing
13 Unlike the Tracepoint based event, this can be added and removed
21 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enable.
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
37  EVENT		: Event name. If omitted, the event name is generated
117 Note that kprobe-event provides the user-memory access syntax but it doesn't
122 Per-Probe Event Filtering
124 Per-probe event filtering feature allows you to set different filter on each
125 probe and gives you what arguments will be shown in trace buffer. If an event
126 name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event
127 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
134   This shows the format of this probe event.
137   You can write filtering rules of this event.
140   This shows the id of this probe event.
143   This allows to install trigger commands which are executed when the event is
146 Event Profiling
150 The first column is event name, the second is the number of probe hits,
159 instead of space. For example, adding myprobe event on do_sys_open like below
170 To add a probe as a new event, write a new definition to kprobe_events
176 1st to 4th arguments as "myprobe" event. Note, which register/stack entry is
186 recording return value as "myretprobe" event.
188 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.
211 You can see that the event has 4 arguments as in the expressions you specified.
225 Right after definition, each event is disabled by default. For tracing these
255 Each line shows when the kernel hits an event, and <- SYMBOL means kernel