Kconfig 8.2 KB
Newer Older
1
#
2 3
# Architectures that offer an FUNCTION_TRACER implementation should
#  select HAVE_FUNCTION_TRACER:
4
#
5

6 7 8
config USER_STACKTRACE_SUPPORT
	bool

9 10 11
config NOP_TRACER
	bool

12
config HAVE_FUNCTION_TRACER
13
	bool
14

15 16 17
config HAVE_FUNCTION_RET_TRACER
	bool

18 19 20 21 22 23 24
config HAVE_FUNCTION_TRACE_MCOUNT_TEST
	bool
	help
	 This gets selected when the arch tests the function_trace_stop
	 variable at the mcount call site. Otherwise, this variable
	 is tested by the called function.

25 26 27
config HAVE_DYNAMIC_FTRACE
	bool

28 29 30
config HAVE_FTRACE_MCOUNT_RECORD
	bool

31 32 33
config HAVE_HW_BRANCH_TRACER
	bool

34 35 36
config TRACER_MAX_TRACE
	bool

S
Steven Rostedt 已提交
37 38 39
config RING_BUFFER
	bool

40 41 42
config TRACING
	bool
	select DEBUG_FS
S
Steven Rostedt 已提交
43
	select RING_BUFFER
44
	select STACKTRACE if STACKTRACE_SUPPORT
45
	select TRACEPOINTS
46
	select NOP_TRACER
47

P
Peter Zijlstra 已提交
48 49
menu "Tracers"

50
config FUNCTION_TRACER
S
Steven Rostedt 已提交
51
	bool "Kernel Function Tracer"
52
	depends on HAVE_FUNCTION_TRACER
53
	depends on DEBUG_KERNEL
S
Steven Rostedt 已提交
54 55
	select FRAME_POINTER
	select TRACING
56
	select CONTEXT_SWITCH_TRACER
S
Steven Rostedt 已提交
57 58 59 60 61 62 63 64
	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.
65

66 67 68 69 70 71 72 73 74 75
config FUNCTION_RET_TRACER
	bool "Kernel Function return Tracer"
	depends on HAVE_FUNCTION_RET_TRACER
	depends on FUNCTION_TRACER
	help
	  Enable the kernel to trace a function at its return.
	  It's first purpose is to trace the duration of functions.
	  This is done by setting the current return address on the thread
	  info structure of the current task.

76 77 78 79 80
config IRQSOFF_TRACER
	bool "Interrupts-off Latency Tracer"
	default n
	depends on TRACE_IRQFLAGS_SUPPORT
	depends on GENERIC_TIME
81
	depends on DEBUG_KERNEL
82 83 84 85 86 87 88 89 90 91 92 93 94
	select TRACE_IRQFLAGS
	select TRACING
	select TRACER_MAX_TRACE
	help
	  This option measures the time spent in irqs-off critical
	  sections, with microsecond accuracy.

	  The default measurement method is a maximum search, which is
	  disabled by default and can be runtime (re-)started
	  via:

	      echo 0 > /debugfs/tracing/tracing_max_latency

95 96 97 98 99 100 101 102 103
	  (Note that kernel size and overhead increases with this option
	  enabled. This option and the preempt-off timing option can be
	  used together or separately.)

config PREEMPT_TRACER
	bool "Preemption-off Latency Tracer"
	default n
	depends on GENERIC_TIME
	depends on PREEMPT
104
	depends on DEBUG_KERNEL
105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120
	select TRACING
	select TRACER_MAX_TRACE
	help
	  This option measures the time spent in preemption off critical
	  sections, with microsecond accuracy.

	  The default measurement method is a maximum search, which is
	  disabled by default and can be runtime (re-)started
	  via:

	      echo 0 > /debugfs/tracing/tracing_max_latency

	  (Note that kernel size and overhead increases with this option
	  enabled. This option and the irqs-off timing option can be
	  used together or separately.)

I
Ingo Molnar 已提交
121 122
config SYSPROF_TRACER
	bool "Sysprof Tracer"
T
Thomas Gleixner 已提交
123
	depends on X86
I
Ingo Molnar 已提交
124 125 126 127 128
	select TRACING
	help
	  This tracer provides the trace needed by the 'Sysprof' userspace
	  tool.

129 130
config SCHED_TRACER
	bool "Scheduling Latency Tracer"
131
	depends on DEBUG_KERNEL
132 133 134 135 136 137 138
	select TRACING
	select CONTEXT_SWITCH_TRACER
	select TRACER_MAX_TRACE
	help
	  This tracer tracks the latency of the highest priority task
	  to be scheduled in, starting from the point it has woken up.

139 140
config CONTEXT_SWITCH_TRACER
	bool "Trace process context switches"
141
	depends on DEBUG_KERNEL
142 143 144 145 146 147
	select TRACING
	select MARKERS
	help
	  This tracer gets called from the context switch and records
	  all switching of tasks.

148 149 150 151
config BOOT_TRACER
	bool "Trace boot initcalls"
	depends on DEBUG_KERNEL
	select TRACING
152
	select CONTEXT_SWITCH_TRACER
153 154
	help
	  This tracer helps developers to optimize boot times: it records
I
Ingo Molnar 已提交
155 156 157 158 159 160 161 162 163 164 165
	  the timings of the initcalls and traces key events and the identity
	  of tasks that can cause boot delays, such as context-switches.

	  Its aim is to be parsed by the /scripts/bootgraph.pl tool to
	  produce pretty graphics about boot inefficiencies, giving a visual
	  representation of the delays during initcalls - but the raw
	  /debug/tracing/trace text output is readable too.

	  ( Note that tracing self tests can't be enabled if this tracer is
	    selected, because the self-tests are an initcall as well and that
	    would invalidate the boot trace. )
166

167
config TRACE_BRANCH_PROFILING
168 169 170 171 172 173 174
	bool "Trace likely/unlikely profiler"
	depends on DEBUG_KERNEL
	select TRACING
	help
	  This tracer profiles all the the likely and unlikely macros
	  in the kernel. It will display the results in:

175
	  /debugfs/tracing/profile_annotated_branch
176 177 178 179 180 181

	  Note: this will add a significant overhead, only turn this
	  on if you need to profile the system's use of these macros.

	  Say N if unsure.

182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197
config PROFILE_ALL_BRANCHES
	bool "Profile all if conditionals"
	depends on TRACE_BRANCH_PROFILING
	help
	  This tracer profiles all branch conditions. Every if ()
	  taken in the kernel is recorded whether it hit or miss.
	  The results will be displayed in:

	  /debugfs/tracing/profile_branch

	  This configuration, when enabled, will impose a great overhead
	  on the system. This should only be enabled when the system
	  is to be analyzed

	  Say N if unsure.

198
config TRACING_BRANCHES
199 200 201 202 203 204 205
	bool
	help
	  Selected by tracers that will trace the likely and unlikely
	  conditions. This prevents the tracers themselves from being
	  profiled. Profiling the tracing infrastructure can only happen
	  when the likelys and unlikelys are not being traced.

206
config BRANCH_TRACER
207
	bool "Trace likely/unlikely instances"
208 209
	depends on TRACE_BRANCH_PROFILING
	select TRACING_BRANCHES
210 211 212 213 214 215 216 217 218 219
	help
	  This traces the events of likely and unlikely condition
	  calls in the kernel.  The difference between this and the
	  "Trace likely/unlikely profiler" is that this is not a
	  histogram of the callers, but actually places the calling
	  events into a running trace buffer to see when and where the
	  events happened, as well as their results.

	  Say N if unsure.

S
Steven Rostedt 已提交
220 221
config STACK_TRACER
	bool "Trace max stack"
222
	depends on HAVE_FUNCTION_TRACER
223
	depends on DEBUG_KERNEL
224
	select FUNCTION_TRACER
S
Steven Rostedt 已提交
225 226
	select STACKTRACE
	help
227 228 229 230 231 232 233 234 235 236 237
	  This special tracer records the maximum stack footprint of the
	  kernel and displays it in debugfs/tracing/stack_trace.

	  This tracer works by hooking into every function call that the
	  kernel executes, and keeping a maximum stack depth value and
	  stack-trace saved. Because this logic has to execute in every
	  kernel function, all the time, this option can slow down the
	  kernel measurably and is generally intended for kernel
	  developers only.

	  Say N if unsure.
S
Steven Rostedt 已提交
238

239 240 241 242 243 244 245 246
config BTS_TRACER
	depends on HAVE_HW_BRANCH_TRACER
	bool "Trace branches"
	select TRACING
	help
	  This tracer records all branches on the system in a circular
	  buffer giving access to the last N branches for each cpu.

247 248
config DYNAMIC_FTRACE
	bool "enable/disable ftrace tracepoints dynamically"
249
	depends on FUNCTION_TRACER
250
	depends on HAVE_DYNAMIC_FTRACE
251
	depends on DEBUG_KERNEL
252 253 254 255 256 257 258
	default y
	help
         This option will modify all the calls to ftrace dynamically
	 (will patch them out of the binary image and replaces them
	 with a No-Op instruction) as they are called. A table is
	 created to dynamically enable them again.

259
	 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but otherwise
260 261 262 263 264 265
	 has native performance as long as no tracing is active.

	 The changes to the code are done by a kernel thread that
	 wakes up once a second and checks to see if any ftrace calls
	 were made. If so, it runs stop_machine (stops all CPUS)
	 and modifies the code to jump over the call to ftrace.
S
Steven Rostedt 已提交
266

267 268 269 270 271
config FTRACE_MCOUNT_RECORD
	def_bool y
	depends on DYNAMIC_FTRACE
	depends on HAVE_FTRACE_MCOUNT_RECORD

S
Steven Rostedt 已提交
272 273 274 275 276
config FTRACE_SELFTEST
	bool

config FTRACE_STARTUP_TEST
	bool "Perform a startup test on ftrace"
277
	depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER
S
Steven Rostedt 已提交
278 279 280 281 282 283
	select FTRACE_SELFTEST
	help
	  This option performs a series of startup tests on ftrace. On bootup
	  a series of tests are made to verify that the tracer is
	  functioning properly. It will do tests on all the configured
	  tracers of ftrace.
P
Peter Zijlstra 已提交
284 285

endmenu