Lines Matching full:tracing
2 Event 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.
20 2. Using Event Tracing
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 # echo ':mod:<module>' > /sys/kernel/tracing/set_event
70 # echo '<match>:mod:<module>' > /sys/kernel/tracing/set_event
77 # echo '<system>:<event>:mod:<module>' > /sys/kernel/tracing/set_event
85 The events available are also listed in /sys/kernel/tracing/events/ hierarchy
90 # echo 1 > /sys/kernel/tracing/events/sched/sched_wakeup/enable
94 # echo 0 > /sys/kernel/tracing/events/sched/sched_wakeup/enable
98 # echo 1 > /sys/kernel/tracing/events/sched/enable
102 # echo 1 > /sys/kernel/tracing/events/enable
153 # cat /sys/kernel/tracing/events/sched/sched_wakeup/format
268 # cd /sys/kernel/tracing/events/sched/sched_wakeup
273 # cd /sys/kernel/tracing/events/signal/signal_generate
280 # cd /sys/kernel/tracing/events/signal/signal_generate
330 # cd /sys/kernel/tracing/events/sched
340 # cd /sys/kernel/tracing/events/sched
351 # cd /sys/kernel/tracing/events/sched
362 exists, will filter all events from tracing any task that does not have the
366 # cd /sys/kernel/tracing
417 /sys/kernel/tracing/events/ftrace/print/trigger
462 /sys/kernel/tracing/events/syscalls/sys_enter_read/trigger
469 /sys/kernel/tracing/events/syscalls/sys_exit_read/trigger
479 /sys/kernel/tracing/events/syscalls/sys_enter_read/trigger
482 /sys/kernel/tracing/events/syscalls/sys_exit_read/trigger
501 /sys/kernel/tracing/events/kmem/kmalloc/trigger
507 /sys/kernel/tracing/events/kmem/kmalloc/trigger
516 /sys/kernel/tracing/events/kmem/kmalloc/trigger
519 /sys/kernel/tracing/events/kmem/kmalloc/trigger
525 /sys/kernel/tracing/events/kmem/kmalloc/trigger
536 queue is unplugged with a depth > 1. If you were tracing a set of
541 /sys/kernel/tracing/events/block/block_unplug/trigger
546 /sys/kernel/tracing/events/block/block_unplug/trigger
551 /sys/kernel/tracing/events/block/block_unplug/trigger
554 /sys/kernel/tracing/events/block/block_unplug/trigger
561 These commands turn tracing on and off when the specified events are
562 hit. The parameter determines how many times the tracing system is
565 The following command turns tracing off the first time a block
566 request queue is unplugged with a depth > 1. If you were tracing a
572 /sys/kernel/tracing/events/block/block_unplug/trigger
574 To always disable tracing when nr_rq > 1::
577 /sys/kernel/tracing/events/block/block_unplug/trigger
582 /sys/kernel/tracing/events/block/block_unplug/trigger
585 /sys/kernel/tracing/events/block/block_unplug/trigger
629 - tracing synthetic events from in-kernel code
746 At this point, the event object is ready to be used for tracing new
749 7.2 Tracing synthetic events from in-kernel code
761 7.2.1 Tracing a synthetic event all at once
828 Before tracing the event, it should be enabled in some way, otherwise
863 7.2.2 Tracing a synthetic event piecewise
999 At this point, the event object is ready to be used for tracing new