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/tracing/available_events.
30 to /sys/kernel/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/tracing/set_event
39 # echo '!sched_wakeup' >> /sys/kernel/tracing/set_event
43 # echo > /sys/kernel/tracing/set_event
47 # echo *:* > /sys/kernel/tracing/set_event
56 # echo 'irq:*' > /sys/kernel/tracing/set_event
61 The events available are also listed in /sys/kernel/tracing/events/ hierarchy
66 # echo 1 > /sys/kernel/tracing/events/sched/sched_wakeup/enable
70 # echo 0 > /sys/kernel/tracing/events/sched/sched_wakeup/enable
74 # echo 1 > /sys/kernel/tracing/events/sched/enable
78 # echo 1 > /sys/kernel/tracing/events/enable
129 # cat /sys/kernel/tracing/events/sched/sched_wakeup/format
244 # cd /sys/kernel/tracing/events/sched/sched_wakeup
249 # cd /sys/kernel/tracing/events/signal/signal_generate
256 # cd /sys/kernel/tracing/events/signal/signal_generate
306 # cd /sys/kernel/tracing/events/sched
316 # cd /sys/kernel/tracing/events/sched
327 # cd /sys/kernel/tracing/events/sched
338 exists, will filter all events from tracing any task that does not have the
342 # cd /sys/kernel/tracing
393 /sys/kernel/tracing/events/ftrace/print/trigger
438 /sys/kernel/tracing/events/syscalls/sys_enter_read/trigger
445 /sys/kernel/tracing/events/syscalls/sys_exit_read/trigger
455 /sys/kernel/tracing/events/syscalls/sys_enter_read/trigger
458 /sys/kernel/tracing/events/syscalls/sys_exit_read/trigger
477 /sys/kernel/tracing/events/kmem/kmalloc/trigger
483 /sys/kernel/tracing/events/kmem/kmalloc/trigger
492 /sys/kernel/tracing/events/kmem/kmalloc/trigger
495 /sys/kernel/tracing/events/kmem/kmalloc/trigger
501 /sys/kernel/tracing/events/kmem/kmalloc/trigger
512 queue is unplugged with a depth > 1. If you were tracing a set of
517 /sys/kernel/tracing/events/block/block_unplug/trigger
522 /sys/kernel/tracing/events/block/block_unplug/trigger
527 /sys/kernel/tracing/events/block/block_unplug/trigger
530 /sys/kernel/tracing/events/block/block_unplug/trigger
537 These commands turn tracing on and off when the specified events are
538 hit. The parameter determines how many times the tracing system is
541 The following command turns tracing off the first time a block
542 request queue is unplugged with a depth > 1. If you were tracing a
548 /sys/kernel/tracing/events/block/block_unplug/trigger
550 To always disable tracing when nr_rq > 1::
553 /sys/kernel/tracing/events/block/block_unplug/trigger
558 /sys/kernel/tracing/events/block/block_unplug/trigger
561 /sys/kernel/tracing/events/block/block_unplug/trigger
605 - tracing synthetic events from in-kernel code
722 At this point, the event object is ready to be used for tracing new
804 Before tracing the event, it should be enabled in some way, otherwise
975 At this point, the event object is ready to be used for tracing new