Lines Matching refs:it

114 # options do not appear when something else selects it. We need the two options
175 	  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
328 	  to be scheduled in, starting from the point it has woken up.
339 	 time, this tracer will detect it. This is useful for testing
356 	 When the tracer is not running, it has no affect on the system,
357 	 but when it is running, it can cause the system to be
362 	 file. Every time a latency is greater than tracing_thresh, it will
420 	  trace recording, as it needs to add some checks to synchronize
451 	  Only enable it if you want to analyse the branching behavior.
452 	  Otherwise keep it disabled.
471 	  taken in the kernel is recorded whether it hit or miss.
645 	  separated out as a stand-alone facility in order to allow it
648 	  selected by tracers that use it.
702 	 When the tracepoint is enabled, it kicks off a kernel thread that
705 	 it took to write to the tracepoint and the next iteration that
707 	 will report the time it took to do the previous tracepoint.
713 	 As it is a tight loop, it benchmarks as hot cache. That's fine because
732 	  This option creates a test to stress the ring buffer and benchmark it.
733 	  It creates its own ring buffer such that it will not interfere with
736 	  10 seconds. Each interval it will print out the number of events
737 	  it recorded and give a rough estimate of how long each iteration took.
739 	  It does not disable interrupts or raise its priority, so it may be
804 	  will trigger events (not necessarily the event it enables)
812 	 It only enables the event and disables it and runs various loads
814 	 up since it runs this on every system call defined.
847 	  as it will write garbage to IO memory starting at a given address.
848 	  However, it should be safe to use on e.g. unused portion of VRAM.