Lines Matching full:event

2 Uprobe-tracer: Uprobe-based Event Tracing
13 Similar to the kprobe-event tracer, this doesn't need to be activated via
16 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enable.
18 However unlike kprobe-event tracer, the uprobe event interface expects the
29   p[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a uprobe
30   r[:[GRP/]EVENT] PATH:OFFSET [FETCHARGS] : Set a return uprobe (uretprobe)
31   p[:[GRP/]EVENT] PATH:OFFSET%return [FETCHARGS] : Set a return uprobe (uretprobe)
32   -:[GRP/]EVENT                           : Clear uprobe or uretprobe event
35   EVENT         : Event name. If omitted, the event name is generated based
58   (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe
79 Event Profiling
81 You can check the total number of probe hits per event via
83 the second is the event name, the third is the number of probe hits.
87  * Add a probe as a new uprobe event, write a new definition to uprobe_events
92  * Add a probe as a new uretprobe event::
96  * Unset registered event::
155 Right after definition, each event is disabled by default. For tracing these
167 Also, you can disable the event by::