Lines Matching full:events
26 The events which are available for tracing can be found in the file
34 .. Note:: '>>' is necessary, otherwise it will firstly disable all the events.
41 To disable all events, echo an empty line to the set_event file::
45 To enable all events, echo ``*:*`` or ``*:`` to the set_event file::
49 The events are organized into subsystems, such as ext4, irq, sched,
52 file. All of the events in a subsystem can be specified via the syntax
53 ``<subsystem>:*``; for example, to enable all irq events, you can use the
61 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
66 # echo 1 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
70 # echo 0 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
72 To enable all events in sched subsystem::
74 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
76 To enable all events::
78 # echo 1 > /sys/kernel/debug/tracing/events/enable
82 - 0 - all events this file affects are disabled
83 - 1 - all events this file affects are enabled
84 - X - there is a mixture of events enabled and disabled
94 event-list is a comma separated list of events. See section 2.1 for event
116 events and correspond to the fields defined in the TRACE_EVENT
129 # cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
156 Trace events can be filtered in the kernel by associating boolean
181 'format' files for trace events (see section 4).
218 # cd /sys/kernel/debug/tracing/events/sched/sched_wakeup
223 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
230 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
258 To clear the filters for all events in a subsystem, write a '0' to the
273 fields can be guaranteed to propagate successfully to all events.
278 Clear the filters on all events in the sched subsystem::
280 # cd /sys/kernel/debug/tracing/events/sched
287 Set a filter using only common fields for all events in the sched
288 subsystem (all events end up with the same filter)::
290 # cd /sys/kernel/debug/tracing/events/sched
297 Attempt to set a filter using a non-common field for all events in the
298 sched subsystem (all events but those that have a prev_pid field retain
301 # cd /sys/kernel/debug/tracing/events/sched
311 The set_event_pid file in the same directory as the top events directory
312 exists, will filter all events from tracing any task that does not have the
318 # echo 1 > events/enable
320 Will only trace events for the current task.
331 Trace events can be made to conditionally invoke trigger 'commands'
333 examples would be enabling or disabling other trace events or invoking
354 This scheme allows triggers to be invoked even for events that aren't
367 /sys/kernel/tracing/events/ftrace/print/trigger
407 For example, the following trigger causes kmalloc events to be
412 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
414 The following trigger causes kmalloc events to stop being traced
419 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
429 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
432 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
451 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
457 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
466 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
469 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
475 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
487 events or functions at the time, the snapshot trace buffer would
488 capture those events when the trigger event occurred::
491 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
496 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
501 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
504 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
511 These commands turn tracing on and off when the specified events are
517 set of events or functions at the time, you could then examine the
518 trace buffer to see the sequence of events that led up to the
522 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
527 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
532 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
535 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
552 In most cases, the command-line interface to trace events is more than
562 or other kernel code to generate user-defined 'synthetic' events at
567 kretprobe events.
579 - tracing synthetic events from in-kernel code
627 trace buffer won't contain unreadable events when the module is
631 events.
634 allows events to be created dynamically and without the need to create
697 events.
699 7.2 Tracing synthetic events from in-kernel code
782 can be used (which is not specific to synthetic events, so does need
950 events.
967 Finally, also similar to synthetic events, the following code can be
986 subystem for creating the corresponding trace events.