Lines Matching refs:tracer
16 Ftrace is an internal tracer designed to help out developers and
21 Although ftrace is typically considered the function tracer, it
77 This is used to set or display the current tracer
91 the tracer or 1 to enable it. Note, this only disables
110 "trace" file is static, and if the tracer is not
118 files. Options also exist to modify how a tracer
205 Have the function tracer only trace a single thread.
216 with the function graph tracer (See the section
251 tracer, or if enabled, the function graph tracer. It will
253 and if run with the function graph tracer, it will also keep
273 Used with the function graph tracer. This is the max depth
304 When the stack tracer is activated, this will display the
311 that was encountered when the stack tracer is activated.
317 functions the stack tracer will check.
500 Function call tracer to trace all kernel functions.
504 Similar to the function tracer except that the
505 function tracer probes the functions on their entry
506 whereas the function graph tracer traces on both entry
545 This is the "trace nothing" tracer. To remove all
550 Examples of using the tracer
563 # tracer: function
586 A header is printed with the tracer name that is represented by
587 the trace. In this case the tracer is "function". Then it shows the
607 # tracer: irqsoff
643 This shows that the current tracer is "irqsoff" tracing the time
806 branch - Enable branch tracing with the tracer.
855 sleep-time - When running function graph tracer, to include
860 graph-time - When running function graph tracer, to include the
866 record-cmd - When any event or tracer is enabled, a hook is enabled
885 # tracer: function
904 functions. This keeps the overhead of the tracer down
908 when the tracer is active.
921 The irqsoff tracer tracks the time for which interrupts are
922 disabled. When a new maximum latency is hit, the tracer saves
938 # tracer: irqsoff
989 # tracer: irqsoff
1071 The preemptoff tracer traces the places that disable preemption.
1072 Like the irqsoff tracer, it records the maximum latency for
1073 which preemption was disabled. The control of preemptoff tracer
1074 is much like the irqsoff tracer.
1084 # tracer: preemptoff
1121 # tracer: preemptoff
1210 The irqsoff tracer will record the total length of
1214 The preemptoff tracer will record the total length of
1221 tracer.
1234 # tracer: preemptirqsoff
1287 # tracer: preemptirqsoff
1403 # tracer: wakeup
1425 The tracer only traces the highest priority task in the system
1450 work well with Real-Time tasks. The wakeup_rt tracer was designed
1452 not recorded because the tracer only records one worst case and
1455 tracer for a while to see that effect).
1457 Since this tracer only deals with RT tasks, we will run this
1469 # tracer: wakeup
1471 # tracer: wakeup_rt
1518 # tracer: wakeup_rt
1643 # tracer: wakeup_rt
1677 This tracer is the function tracer. Enabling the function tracer
1679 ftrace_enabled is set; otherwise this tracer is a nop.
1688 # tracer: function
1710 Note: function tracer uses ring buffers to store the above
1746 # tracer: function
1758 # tracer: function
1871 function graph tracer
1874 This tracer is similar to the function tracer except that it
1877 task_struct. On function entry the tracer overwrites the return
1888 This tracer is useful in several situations:
1903 # tracer: function_graph
2009 # tracer: function_graph
2091 You might find other useful features for this tracer in the
2183 # tracer: function
2226 # tracer: function
2311 # tracer: function
2338 Dynamic ftrace with the function graph tracer
2342 function tracer and the function-graph-tracer, there are some
2343 special features only available in the function-graph tracer.
2403 function tracer. By default it is enabled (when function tracing is
2553 # tracer: function
2673 # tracer: nop
2690 # tracer: nop
2706 If you try to use this snapshot feature when current tracer is
2743 Notice that none of the function tracer files are there, nor is
2803 # tracer: nop
2851 a function tracer, it makes it convenient to check the stack size
2852 at every function call. This is enabled via the stack tracer.
2892 are not tested by the stack tracer when -mfentry is used.