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
81 	  but does not want them included in the ftrace locations.
92 	  See Documentation/trace/ftrace-design.rst
114 	  of ftrace locations.
227 	  Enable developer to setup ftrace subsystem via supplemental
274 	  See Documentation/trace/ftrace.rst
306 	  compile time, a table is made of all the locations that ftrace
366 	  This option enables kernel function probe (fprobe) based on ftrace.
623 	  ftrace interface, e.g.:
745 	  Tracing also is possible using the ftrace interface, e.g.:
763 	  exit via ftrace interface. The syntax is same as the kprobe events
789 	  on the fly via the ftrace interface. See
804 	  This is only for the developers who want to debug ftrace itself
807 	  If kprobes can use ftrace instead of breakpoint, ftrace related
813 	  events on ftrace functions for debugging ftrace by itself.
1008 	  any other users of the ring buffer (such as ftrace). It then creates
1072 	bool "Validate RCU is on during ftrace execution"
1078 	  ftrace (and other users of ftrace_test_recursion_trylock()) are not
1093 	  place where recursion was detected into the ftrace "recursed_functions"
1099 	bool "Enable GCOV profiling on ftrace subsystem"
1102 	  Enable GCOV profiling on ftrace subsystem for checking
1107 	  Note that on a kernel compiled with this config, ftrace will
1114 	bool "Perform a startup test on ftrace"
1118 	  This option performs a series of startup tests on ftrace. On bootup
1121 	  tracers of ftrace.
1146        bool "Verify compile time sorting of ftrace functions"
1151 	 where the ftrace knows where to patch functions for tracing