[linux-2.6-block.git] / kernel / trace / Kconfig

#
# Architectures that offer an FTRACE implementation should select HAVE_FTRACE:
#
config HAVE_FTRACE
	bool

config TRACING
	bool
	select DEBUG_FS

config FTRACE
	bool "Kernel Function Tracer"
	depends on DEBUG_KERNEL && HAVE_FTRACE
	select FRAME_POINTER
	select TRACING
	help
	  Enable the kernel to trace every kernel function. This is done
	  by using a compiler feature to insert a small, 5-byte No-Operation
	  instruction to the beginning of every kernel function, which NOP
	  sequence is then dynamically patched into a tracer call when
	  tracing is enabled by the administrator. If it's runtime disabled
	  (the bootup default), then the overhead of the instructions is very
	  small and not measurable even in micro-benchmarks.
Commit	Line	Data
16444a8a ACM	1	#
	2	# Architectures that offer an FTRACE implementation should select HAVE_FTRACE:
	3	#
	4	config HAVE_FTRACE
	5	bool
bc0c38d1 SR	6
	7	config TRACING
	8	bool
	9	select DEBUG_FS
	10
1b29b018 SR	11	config FTRACE
	12	bool "Kernel Function Tracer"
	13	depends on DEBUG_KERNEL && HAVE_FTRACE
	14	select FRAME_POINTER
	15	select TRACING
	16	help
	17	Enable the kernel to trace every kernel function. This is done
	18	by using a compiler feature to insert a small, 5-byte No-Operation
	19	instruction to the beginning of every kernel function, which NOP
	20	sequence is then dynamically patched into a tracer call when
	21	tracing is enabled by the administrator. If it's runtime disabled
	22	(the bootup default), then the overhead of the instructions is very
	23	small and not measurable even in micro-benchmarks.