Lines Matching refs:ftrace

27 	  See Documentation/trace/ftrace-design.rst
32 	  See Documentation/trace/ftrace-design.rst
45 	  See Documentation/trace/ftrace-design.rst
84 	  but does not want them included in the ftrace locations.
95 	  See Documentation/trace/ftrace-design.rst
117 	  of ftrace locations.
231 	  Enable developer to setup ftrace subsystem via supplemental
278 	  See Documentation/trace/ftrace.rst
310 	  compile time, a table is made of all the locations that ftrace
370 	  This option enables kernel function probe (fprobe) based on ftrace.
623 	  ftrace interface, e.g.:
748 	  Tracing also is possible using the ftrace interface, e.g.:
766 	  exit via ftrace interface. The syntax is same as the kprobe events
792 	  on the fly via the ftrace interface. See
807 	  This is only for the developers who want to debug ftrace itself
810 	  If kprobes can use ftrace instead of breakpoint, ftrace related
816 	  events on ftrace functions for debugging ftrace by itself.
1011 	  any other users of the ring buffer (such as ftrace). It then creates
1075 	bool "Validate RCU is on during ftrace execution"
1081 	  ftrace (and other users of ftrace_test_recursion_trylock()) are not
1096 	  place where recursion was detected into the ftrace "recursed_functions"
1102 	bool "Enable GCOV profiling on ftrace subsystem"
1105 	  Enable GCOV profiling on ftrace subsystem for checking
1110 	  Note that on a kernel compiled with this config, ftrace will
1117 	bool "Perform a startup test on ftrace"
1121 	  This option performs a series of startup tests on ftrace. On bootup
1124 	  tracers of ftrace.
1149        bool "Verify compile time sorting of ftrace functions"
1154 	 where the ftrace knows where to patch functions for tracing