Lines Matching refs:on

78        depends on HAVE_FTRACE_NMI_ENTER
129 	depends on TRACE_IRQFLAGS_SUPPORT || PPC32
130 	depends on STACKTRACE_SUPPORT
145 	depends on HAVE_FUNCTION_TRACER
160 	depends on HAVE_FUNCTION_GRAPH_TRACER
161 	depends on FUNCTION_TRACER
162 	depends on !X86_32 || !CC_OPTIMIZE_FOR_SIZE
170 	  address on the current task structure into a stack of calls.
176 	depends on TRACE_IRQFLAGS_SUPPORT
177 	depends on !ARCH_USES_GETTIMEOFFSET
201 	depends on !ARCH_USES_GETTIMEOFFSET
202 	depends on PREEMPT
234 	depends on !GENERIC_TRACER
243 	depends on HAVE_SYSCALL_TRACEPOINTS
261 	depends on TRACER_SNAPSHOT
318 	  on if you need to profile the system's use of these macros.
333 	  on the system. This should only be enabled when the system
347 	depends on TRACE_BRANCH_PROFILING
361 	depends on HAVE_FUNCTION_TRACER
375 	  To enable the stack tracer on bootup, pass in 'stacktrace'
376 	  on the kernel command line.
385 	depends on SYSFS
386 	depends on BLOCK
394 	  on a given queue. Tracing allows you to see any traffic happening
395 	  on a block device queue. For more information (and the userspace
409 	depends on KPROBES
410 	depends on HAVE_REGS_AND_STACK_ACCESS_API
417 	  on the fly via the ftrace interface. See
428 	depends on ARCH_SUPPORTS_UPROBES
429 	depends on MMU
435 	  This allows the user to add tracing events on top of userspace
436 	  dynamic events (similar to tracepoints) on the fly via the trace
440 	  of perf tools on user space applications.
447 	depends on FUNCTION_TRACER
448 	depends on HAVE_DYNAMIC_FTRACE
453 	  replace them with a No-Op instruction) on boot up. During
470 	depends on DYNAMIC_FTRACE
471 	depends on HAVE_DYNAMIC_FTRACE_WITH_REGS
475 	depends on FUNCTION_TRACER
489 	depends on DYNAMIC_FTRACE
490 	depends on HAVE_FTRACE_MCOUNT_RECORD
496 	bool "Perform a startup test on ftrace"
497 	depends on GENERIC_TRACER
500 	  This option performs a series of startup tests on ftrace. On bootup
502 	  functioning properly. It will do tests on all the configured
506 	bool "Run selftest on syscall events"
507 	depends on FTRACE_STARTUP_TEST
512 	 up since it runs this on every system call defined.
519 	depends on HAVE_MMIOTRACE_SUPPORT && PCI
532 	depends on MMIOTRACE && m
536 	  However, it should be safe to use on e.g. unused portion of VRAM.
542 	depends on RING_BUFFER
558        depends on RING_BUFFER
560          Run a simple self test on the ring buffer on boot up. Late in the