Lines Matching refs:ftrace

27 	  See Documentation/trace/ftrace-design.rst
32 See Documentation/trace/ftrace-design.rst
40 See Documentation/trace/ftrace-design.rst
64 but does not want them included in the ftrace locations.
69 See Documentation/trace/ftrace-design.rst
74 See Documentation/trace/ftrace-design.rst
96 of ftrace locations.
196 Enable developer to setup ftrace subsystem via supplemental
243 See Documentation/trace/ftrace.rst
254 compile time, a table is made of all the locations that ftrace
295 This option enables kernel function probe (fprobe) based on ftrace.
538 ftrace interface, e.g.:
660 Tracing also is possible using the ftrace interface, e.g.:
678 exit via ftrace interface. The syntax is same as the kprobe events
704 on the fly via the ftrace interface. See
719 This is only for the developers who want to debug ftrace itself
722 If kprobes can use ftrace instead of breakpoint, ftrace related
728 events on ftrace functions for debugging ftrace by itself.
914 any other users of the ring buffer (such as ftrace). It then creates
986 place where recursion was detected into the ftrace "recursed_functions"
992 bool "Enable GCOV profiling on ftrace subsystem"
995 Enable GCOV profiling on ftrace subsystem for checking
1000 Note that on a kernel compiled with this config, ftrace will
1007 bool "Perform a startup test on ftrace"
1011 This option performs a series of startup tests on ftrace. On bootup
1014 tracers of ftrace.
1039 bool "Verify compile time sorting of ftrace functions"
1044 where the ftrace knows where to patch functions for tracing