Lines Matching refs:tracing
13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
17 tracing information is saved into the tracing buffer, and how the
18 tracing information should be printed.
26 The events which are available for tracing can be found in the file
27 /sys/kernel/debug/tracing/available_events.
30 to /sys/kernel/debug/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
39 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
43 # echo > /sys/kernel/debug/tracing/set_event
47 # echo *:* > /sys/kernel/debug/tracing/set_event
56 # echo 'irq:*' > /sys/kernel/debug/tracing/set_event
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
74 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
78 # echo 1 > /sys/kernel/debug/tracing/events/enable
129 # cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
209 # cd /sys/kernel/debug/tracing/events/sched/sched_wakeup
214 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
221 # cd /sys/kernel/debug/tracing/events/signal/signal_generate
261 # cd /sys/kernel/debug/tracing/events/sched
271 # cd /sys/kernel/debug/tracing/events/sched
282 # cd /sys/kernel/debug/tracing/events/sched
293 exists, will filter all events from tracing any task that does not have the
297 # cd /sys/kernel/debug/tracing
348 /sys/kernel/tracing/events/ftrace/print/trigger
393 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
400 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
410 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
413 /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
432 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
438 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
447 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
450 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
456 /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
467 queue is unplugged with a depth > 1. If you were tracing a set of
472 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
477 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
482 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
485 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
492 These commands turn tracing on and off when the specified events are
493 hit. The parameter determines how many times the tracing system is
496 The following command turns tracing off the first time a block
497 request queue is unplugged with a depth > 1. If you were tracing a
503 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
505 To always disable tracing when nr_rq > 1::
508 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
513 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
516 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
560 - tracing synthetic events from in-kernel code
677 At this point, the event object is ready to be used for tracing new
759 Before tracing the event, it should be enabled in some way, otherwise
930 At this point, the event object is ready to be used for tracing new