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.
210 with the function graph tracer (See the section
245 tracer, or if enabled, the function graph tracer. It will
247 and if run with the function graph tracer, it will also keep
267 Used with the function graph tracer. This is the max depth
298 When the stack tracer is activated, this will display the
305 that was encountered when the stack tracer is activated.
311 functions the stack tracer will check.
489 Function call tracer to trace all kernel functions.
493 Similar to the function tracer except that the
494 function tracer probes the functions on their entry
495 whereas the function graph tracer traces on both entry
534 This is the "trace nothing" tracer. To remove all
539 Examples of using the tracer
552 # tracer: function
575 A header is printed with the tracer name that is represented by
576 the trace. In this case the tracer is "function". Then it shows the
596 # tracer: irqsoff
632 This shows that the current tracer is "irqsoff" tracing the time
793 branch - Enable branch tracing with the tracer.
842 sleep-time - When running function graph tracer, to include
847 graph-time - When running function graph tracer, to include the
853 record-cmd - When any event or tracer is enabled, a hook is enabled
872 # tracer: function
891 functions. This keeps the overhead of the tracer down
895 when the tracer is active.
908 The irqsoff tracer tracks the time for which interrupts are
909 disabled. When a new maximum latency is hit, the tracer saves
925 # tracer: irqsoff
976 # tracer: irqsoff
1058 The preemptoff tracer traces the places that disable preemption.
1059 Like the irqsoff tracer, it records the maximum latency for
1060 which preemption was disabled. The control of preemptoff tracer
1061 is much like the irqsoff tracer.
1071 # tracer: preemptoff
1108 # tracer: preemptoff
1197 The irqsoff tracer will record the total length of
1201 The preemptoff tracer will record the total length of
1208 tracer.
1221 # tracer: preemptirqsoff
1274 # tracer: preemptirqsoff
1390 # tracer: wakeup
1412 The tracer only traces the highest priority task in the system
1437 work well with Real-Time tasks. The wakeup_rt tracer was designed
1439 not recorded because the tracer only records one worst case and
1442 tracer for a while to see that effect).
1444 Since this tracer only deals with RT tasks, we will run this
1456 # tracer: wakeup
1458 # tracer: wakeup_rt
1505 # tracer: wakeup_rt
1630 # tracer: wakeup_rt
1664 This tracer is the function tracer. Enabling the function tracer
1666 ftrace_enabled is set; otherwise this tracer is a nop.
1675 # tracer: function
1697 Note: function tracer uses ring buffers to store the above
1733 # tracer: function
1745 # tracer: function
1858 function graph tracer
1861 This tracer is similar to the function tracer except that it
1864 task_struct. On function entry the tracer overwrites the return
1875 This tracer is useful in several situations:
1890 # tracer: function_graph
1973 # tracer: function_graph
2055 You might find other useful features for this tracer in the
2147 # tracer: function
2190 # tracer: function
2275 # tracer: function
2302 Dynamic ftrace with the function graph tracer
2306 function tracer and the function-graph-tracer, there are some
2307 special features only available in the function-graph tracer.
2367 function tracer. By default it is enabled (when function tracing is
2500 # tracer: function
2620 # tracer: nop
2637 # tracer: nop
2653 If you try to use this snapshot feature when current tracer is
2690 Notice that none of the function tracer files are there, nor is
2750 # tracer: nop
2798 a function tracer, it makes it convenient to check the stack size
2799 at every function call. This is enabled via the stack tracer.
2839 are not tested by the stack tracer when -mfentry is used.