Lines Matching refs:it

93          An architecture selects this if it sorts the mcount_loc section
140 # options do not appear when something else selects it. We need the two options
201 	  tracing is enabled by the administrator. If it's runtime disabled
295 	  kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
300 	  then it will not have any overhead while the stack tracer
373 	  to be scheduled in, starting from the point it has woken up.
385 	 time, this tracer will detect it. This is useful for testing
402 	 When the tracer is not running, it has no affect on the system,
403 	 but when it is running, it can cause the system to be
408 	 file. Every time a latency is greater than tracing_thresh, it will
529 	  trace recording, as it needs to add some checks to synchronize
560 	  Only enable it if you want to analyse the branching behavior.
561 	  Otherwise keep it disabled.
580 	  taken in the kernel is recorded whether it hit or miss.
755 	  separated out as a stand-alone facility in order to allow it
758 	  selected by tracers that use it.
827 	 When the tracepoint is enabled, it kicks off a kernel thread that
830 	 it took to write to the tracepoint and the next iteration that
832 	 will report the time it took to do the previous tracepoint.
838 	 As it is a tight loop, it benchmarks as hot cache. That's fine because
857 	  This option creates a test to stress the ring buffer and benchmark it.
858 	  It creates its own ring buffer such that it will not interfere with
861 	  10 seconds. Each interval it will print out the number of events
862 	  it recorded and give a rough estimate of how long each iteration took.
864 	  It does not disable interrupts or raise its priority, so it may be
903 	  it adds overhead. This option will create a file in the tracefs
925 	# default y, because it is coupled with FTRACE_RECORD_RECURSION
929 	  recursion happens it wont cause harm because of the protection,
930 	  but it does cause an unwanted overhead. Enabling this option will
968 	  will trigger events (not necessarily the event it enables)
976 	 It only enables the event and disables it and runs various loads
978 	 up since it runs this on every system call defined.
991 	 is not done correctly, it will cause non-deterministic failures.
1035 	  Do not use it on production systems.
1038 	  still want it enabled. Otherwise say N
1045 	  as it will write garbage to IO memory starting at a given address.
1046 	  However, it should be safe to use on e.g. unused portion of VRAM.