Lines Matching refs:in

50 	 by default, even without setting the REGS flag in the ftrace_ops.
58 	  but does not want them included in the ftrace locations.
203 	  small and not measurable even in micro-benchmarks (at least on
235 	  See the files in /sys/kernel/debug/tracing:
279 	  in debugfs called function_profile_enabled which defaults to zero.
281 	  zero is entered, profiling stops. A "functions" file is created in
285 	  If in doubt, say N.
295 	  kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
303 	  To enable the stack tracer on bootup, pass in 'stacktrace'
328 	  This option measures the time spent in irqs-off critical
352 	  This option measures the time spent in preemption-off critical
373 	  to be scheduled in, starting from the point it has woken up.
382 	 spinning in a loop looking for interruptions caused by
388 	 Some files are created in the tracing directory when this
391 	   hwlat_detector/width   - time in usecs for how long to spin for
392 	   hwlat_detector/window  - time in usecs between the start of each
396 	 for "width" microseconds in every "window" cycle. It will not spin
400 	 The output will appear in the trace and trace_pipe files.
407 	 To enable this tracer, echo in "hwlat" into the current_tracer
441 	  The output will appear in the trace and trace_pipe files.
443 	  To enable this tracer, echo in "osnoise" into the current_tracer
492 	  This tracer hooks to various trace points in the kernel,
549 	 The "all branch" profiler will profile every if-statement in the
568 	  in the kernel. It will display the results in:
580 	  taken in the kernel is recorded whether it hit or miss.
581 	  The results will be displayed in:
589 	  is to be analyzed in much detail.
606 	  calls in the kernel.  The difference between this and the
674 	  Note that this might let you shoot yourself in the foot.
755 	  separated out as a stand-alone facility in order to allow it
767 	  used to combine data from other trace events or in fact any
770 	  by way of an in-kernel API.
775 	  If in doubt, say N.
790 	  If in doubt, say N.
812 	  If in doubt, say N.
839 	 we care most about hot paths that are probably in cache already.
878 	To fix this, there's a special macro in the kernel that can be used
886 	in the tracing directory called "eval_map" that will show the
898 	bool "Record functions that recurse in function tracing"
903 	  it adds overhead. This option will create a file in the tracefs
917 	  listed in the "recursed_functions" file, that lists all
919 	  This file can be reset, but the limit can not change in
923 	bool "Record functions that recurse in the ring buffer"
966 	  This option performs a test on all trace events in the system.
993 	 are in deed sorted and will warn if they are not.
1001 	 Run a simple self test on the ring buffer on boot up. Late in the
1070 	tristate "Test module for in-kernel synthetic event generation"
1074           functionality of in-kernel synthetic event definition and
1083 	tristate "Test module for in-kernel kprobe event generation"
1087           functionality of in-kernel kprobe event definition.