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
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
280 # cd /sys/kernel/debug/tracing/events/sched
290 # cd /sys/kernel/debug/tracing/events/sched
301 # cd /sys/kernel/debug/tracing/events/sched
312 exists, will filter all events from tracing any task that does not have the
316 # cd /sys/kernel/debug/tracing
367 /sys/kernel/tracing/events/ftrace/print/trigger
412 /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
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
486 queue is unplugged with a depth > 1. If you were tracing a set of
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
512 hit. The parameter determines how many times the tracing system is
515 The following command turns tracing off the first time a block
516 request queue is unplugged with a depth > 1. If you were tracing a
522 /sys/kernel/debug/tracing/events/block/block_unplug/trigger
524 To always disable tracing when nr_rq > 1::
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
579 - tracing synthetic events from in-kernel code
696 At this point, the event object is ready to be used for tracing new
778 Before tracing the event, it should be enabled in some way, otherwise
949 At this point, the event object is ready to be used for tracing new