Lines Matching refs:event

12 functions). Unlike the Tracepoint based event, this can be added and removed
30  EVENT		: Event name. If omitted, the event name is generated
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
70 name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event
78   This shows the format of this probe event.
81   You can write filtering rules of this event.
84   This shows the id of this probe event.
91  The first column is event name, the second is the number of probe hits,
97 To add a probe as a new event, write a new definition to kprobe_events
103 1st to 4th arguments as "myprobe" event. Note, which register/stack entry is
112 recording return value as "myretprobe" event.
136  You can see that the event has 4 arguments as in the expressions you specified.
148  Right after definition, each event is disabled by default. For tracing these
169  Each line shows when the kernel hits an event, and <- SYMBOL means kernel