Lines Matching refs:tracing
22 is really a frame work of several assorted tracing utilities.
23 There's latency tracing to examine what occurs between interrupts
27 One of the most common uses of ftrace is the event tracing.
60 Any selected ftrace option will also create a directory called tracing
62 the ftrace directory (cd /sys/kernel/debug/tracing) and will only concentrate
64 the extended "/sys/kernel/debug/tracing" path name.
69 "tracing". This directory contains the control and output files
92 writing to the ring buffer, the tracing overhead may
103 file is meant to be streamed with live tracing.
165 If a process is performing the tracing, and the ring buffer
169 be resized to its minimum size. Having a process that is tracing
174 It may also stop tracing if disable_on_free option is set.
187 function profiler (mcount). This lets tracing be configured
209 Set a "trigger" function where tracing should start
255 A directory that holds different tracing stats.
323 Usual clocks for tracing:
535 tracers from tracing simply echo "nop" into
632 This shows that the current tracer is "irqsoff" tracing the time
793 branch - Enable branch tracing with the tracer.
858 impact of tracing.
866 disable_on_free - When the free_buffer is closed, tracing will
888 function-trace - The latency tracers will enable function tracing
1045 enabling function tracing, we incur an added overhead. This
1268 function tracing, we do not know if interrupts were enabled
1376 One common case that people are interested in tracing is the
1378 Now for non Real-Time tasks, this can be arbitrary. But tracing
1381 Without function tracing:
1413 to avoid tracing the normal circumstances. Here we see that
1440 tracing non-RT tasks that are unpredictable will overwrite the
1483 is before the actual "switch", we stop the tracing when the recorded task
1608 This isn't that big of a trace, even with function tracing enabled,
1615 Latency tracing and events
1617 As function tracing can induce a much larger latency, but without
1700 the tracing could have overwritten the data that you wanted to
1702 tracing directly from a program. This allows you to stop the
1703 tracing at the point that you hit the part that you are
1704 interested in. To disable the tracing directly from a C program,
1720 Single thread tracing
1800 strcat(debugfs, "/tracing/");
1849 echo nop > $debugfs/tracing/current_tracer
1850 echo 0 > $debugfs/tracing/tracing_on
1851 echo $$ > $debugfs/tracing/set_ftrace_pid
1852 echo function > $debugfs/tracing/current_tracer
1853 echo 1 > $debugfs/tracing/tracing_on
1920 function calls while cpu tracing switch.
2056 following "dynamic ftrace" section such as tracing only specific
2063 virtually no overhead when function tracing is disabled. The way
2092 When tracing is enabled, the process of modifying the function
2117 tracing of specified functions. They are:
2299 We can see that there's no more lock or preempt tracing.
2367 function tracer. By default it is enabled (when function tracing is
2368 enabled in the kernel). If it is disabled, all function tracing is
2370 also for any other uses (perf, kprobes, stack tracing, profiling, etc).
2411 These commands turn tracing on and off when the specified
2413 tracing system is turned on and off. If unspecified, there is
2414 no limit. For example, to disable tracing when a schedule bug
2419 To always disable tracing when __schedule_bug is hit:
2450 function tracing callbacks are very sensitive, when these commands
2489 the effect on the tracing is different. Every read from
2588 in time without stopping tracing. Ftrace swaps the current
2589 buffer with a spare buffer, and tracing continues in the new
2592 The following debugfs files in "tracing" are related to this
2602 System"). Both reads snapshot and tracing are executable
2665 In the debugfs tracing directory is a directory called "instances".
2677 As you can see, the new directory looks similar to the tracing directory
2683 same name in the tracing directory except the buffer that is used
2774 the function tracing. The foo instance displays wakeups and task
2801 CONFIG_STACK_TRACER enables the ftrace stack tracing functionality.