Lines Matching refs:it

110 # options do not appear when something else selects it. We need the two options
170 	  tracing is enabled by the administrator. If it's runtime disabled
248 	  kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
253 	  then it will not have any overhead while the stack tracer
326 	  to be scheduled in, starting from the point it has woken up.
338 	 time, this tracer will detect it. This is useful for testing
355 	 When the tracer is not running, it has no affect on the system,
356 	 but when it is running, it can cause the system to be
361 	 file. Every time a latency is greater than tracing_thresh, it will
482 	  trace recording, as it needs to add some checks to synchronize
513 	  Only enable it if you want to analyse the branching behavior.
514 	  Otherwise keep it disabled.
533 	  taken in the kernel is recorded whether it hit or miss.
707 	  separated out as a stand-alone facility in order to allow it
710 	  selected by tracers that use it.
764 	 When the tracepoint is enabled, it kicks off a kernel thread that
767 	 it took to write to the tracepoint and the next iteration that
769 	 will report the time it took to do the previous tracepoint.
775 	 As it is a tight loop, it benchmarks as hot cache. That's fine because
794 	  This option creates a test to stress the ring buffer and benchmark it.
795 	  It creates its own ring buffer such that it will not interfere with
798 	  10 seconds. Each interval it will print out the number of events
799 	  it recorded and give a rough estimate of how long each iteration took.
801 	  It does not disable interrupts or raise its priority, so it may be
840 	  it adds overhead. This option will create a file in the tracefs
862 	# default y, because it is coupled with FTRACE_RECORD_RECURSION
866 	  recursion happens it wont cause harm because of the protection,
867 	  but it does cause an unwanted overhead. Enabling this option will
905 	  will trigger events (not necessarily the event it enables)
913 	 It only enables the event and disables it and runs various loads
915 	 up since it runs this on every system call defined.
958 	  Do not use it on production systems.
961 	  still want it enabled. Otherwise say N
968 	  as it will write garbage to IO memory starting at a given address.
969 	  However, it should be safe to use on e.g. unused portion of VRAM.