Lines Matching refs:events
24 The events which are available for tracing can be found in the file
33 all the events. ]
40 To disable all events, echo an empty line to the set_event file:
44 To enable all events, echo '*:*' or '*:' to the set_event file:
48 The events are organized into subsystems, such as ext4, irq, sched,
51 file. All of the events in a subsystem can be specified via the syntax
52 "<subsystem>:*"; for example, to enable all irq events, you can use the
60 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
65 # echo 1 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
69 # echo 0 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
71 To enable all events in sched subsystem:
73 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
75 To enable all events:
77 # echo 1 > /sys/kernel/debug/tracing/events/enable
81 0 - all events this file affects are disabled
82 1 - all events this file affects are enabled
83 X - there is a mixture of events enabled and disabled
93 event-list is a comma separated list of events. See section 2.1 for event
115 events and correspond to the fields defined in the TRACE_EVENT
128 # cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
155 Trace events can be filtered in the kernel by associating boolean
180 'format' files for trace events (see section 4).
211 # cd /sys/kernel/debug/tracing/events/sched/sched_wakeup
216 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
223 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
241 To clear the filters for all events in a subsystem, write a '0' to the
256 fields can be guaranteed to propagate successfully to all events.
261 Clear the filters on all events in the sched subsystem:
263 # cd /sys/kernel/debug/tracing/events/sched
270 Set a filter using only common fields for all events in the sched
271 subsystem (all events end up with the same filter):
273 # cd /sys/kernel/debug/tracing/events/sched
280 Attempt to set a filter using a non-common field for all events in the
281 sched subsystem (all events but those that have a prev_pid field retain
284 # cd /sys/kernel/debug/tracing/events/sched
294 Trace events can be made to conditionally invoke trigger 'commands'
296 examples would be enabling or disabling other trace events or invoking
317 This scheme allows triggers to be invoked even for events that aren't
365 For example, the following trigger causes kmalloc events to be
370 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
372 The following trigger causes kmalloc events to stop being traced
377 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
387 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
390 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
409 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
415 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
424 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
427 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
433 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
445 events or functions at the time, the snapshot trace buffer would
446 capture those events when the trigger event occurred:
449 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
454 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
459 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
462 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
469 These commands turn tracing on and off when the specified events are
475 set of events or functions at the time, you could then examine the
476 trace buffer to see the sequence of events that led up to the
480 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
485 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
490 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
493 /sys/kernel/debug/tracing/events/block/block_unplug/trigger