Lines Matching refs:tracing
11 using the event tracing infrastructure.
13 Not all tracepoints can be traced using the event tracing system;
15 tracing information is saved into the tracing buffer, and how the
16 tracing information should be printed.
24 The events which are available for tracing can be found in the file
25 /sys/kernel/debug/tracing/available_events.
28 to /sys/kernel/debug/tracing/set_event. For example:
30 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
38 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
42 # echo > /sys/kernel/debug/tracing/set_event
46 # echo *:* > /sys/kernel/debug/tracing/set_event
55 # echo 'irq:*' > /sys/kernel/debug/tracing/set_event
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
73 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
77 # echo 1 > /sys/kernel/debug/tracing/events/enable
128 # cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
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
263 # cd /sys/kernel/debug/tracing/events/sched
273 # cd /sys/kernel/debug/tracing/events/sched
284 # cd /sys/kernel/debug/tracing/events/sched
370 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
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
444 queue is unplugged with a depth > 1. If you were tracing a set of
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
470 hit. The parameter determines how many times the tracing system is
473 The following command turns tracing off the first time a block
474 request queue is unplugged with a depth > 1. If you were tracing a
480 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
482 To always disable tracing when nr_rq > 1 :
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