Kconfig 10.7 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
config HAVE_FUNCTION_GRAPH_TRACER
16 17
	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
config FUNCTION_GRAPH_TRACER
	bool "Kernel Function Graph Tracer"
	depends on HAVE_FUNCTION_GRAPH_TRACER
69
	depends on FUNCTION_TRACER
70
	default y
71
	help
72 73 74 75 76 77 78
	  Enable the kernel to trace a function at both its return
	  and its entry.
	  It's first purpose is to trace the duration of functions and
	  draw a call graph for each thread with some informations like
	  the return value.
	  This is done by setting the current return address on the current
	  task structure into a stack of calls.
79

80 81 82 83 84
config IRQSOFF_TRACER
	bool "Interrupts-off Latency Tracer"
	default n
	depends on TRACE_IRQFLAGS_SUPPORT
	depends on GENERIC_TIME
85
	depends on DEBUG_KERNEL
86 87 88 89 90 91 92 93 94 95 96 97 98
	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

99 100 101 102 103 104 105 106 107
	  (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
108
	depends on DEBUG_KERNEL
109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
	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 已提交
125 126
config SYSPROF_TRACER
	bool "Sysprof Tracer"
T
Thomas Gleixner 已提交
127
	depends on X86
I
Ingo Molnar 已提交
128 129 130 131 132
	select TRACING
	help
	  This tracer provides the trace needed by the 'Sysprof' userspace
	  tool.

133 134
config SCHED_TRACER
	bool "Scheduling Latency Tracer"
135
	depends on DEBUG_KERNEL
136 137 138 139 140 141 142
	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.

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

152 153 154 155
config BOOT_TRACER
	bool "Trace boot initcalls"
	depends on DEBUG_KERNEL
	select TRACING
156
	select CONTEXT_SWITCH_TRACER
157 158
	help
	  This tracer helps developers to optimize boot times: it records
I
Ingo Molnar 已提交
159 160 161 162 163 164 165 166 167 168 169
	  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. )
170

171
config TRACE_BRANCH_PROFILING
172 173 174 175 176 177 178
	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:

179
	  /debugfs/tracing/profile_annotated_branch
180 181 182 183 184 185

	  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.

186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201
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.

202
config TRACING_BRANCHES
203 204 205 206 207 208 209
	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.

210
config BRANCH_TRACER
211
	bool "Trace likely/unlikely instances"
212 213
	depends on TRACE_BRANCH_PROFILING
	select TRACING_BRANCHES
214 215 216 217 218 219 220 221 222 223
	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.

224 225 226 227 228 229 230 231 232 233 234
config POWER_TRACER
	bool "Trace power consumption behavior"
	depends on DEBUG_KERNEL
	depends on X86
	select TRACING
	help
	  This tracer helps developers to analyze and optimize the kernels
	  power management decisions, specifically the C-state and P-state
	  behavior.


S
Steven Rostedt 已提交
235 236
config STACK_TRACER
	bool "Trace max stack"
237
	depends on HAVE_FUNCTION_TRACER
238
	depends on DEBUG_KERNEL
239
	select FUNCTION_TRACER
S
Steven Rostedt 已提交
240 241
	select STACKTRACE
	help
242 243 244 245 246
	  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
247 248 249 250 251 252 253 254 255
	  stack-trace saved.  If this is configured with DYNAMIC_FTRACE
	  then it will not have any overhead while the stack tracer
	  is disabled.

	  To enable the stack tracer on bootup, pass in 'stacktrace'
	  on the kernel command line.

	  The stack tracer can also be enabled or disabled via the
	  sysctl kernel.stack_tracer_enabled
256 257

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

259
config HW_BRANCH_TRACER
260
	depends on HAVE_HW_BRANCH_TRACER
261
	bool "Trace hw branches"
262 263 264 265 266
	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.

267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286
config KMEMTRACE
	bool "Trace SLAB allocations"
	select TRACING
	help
	  kmemtrace provides tracing for slab allocator functions, such as
	  kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected
	  data is then fed to the userspace application in order to analyse
	  allocation hotspots, internal fragmentation and so on, making it
	  possible to see how well an allocator performs, as well as debug
	  and profile kernel code.

	  This requires an userspace application to use. See
	  Documentation/vm/kmemtrace.txt for more information.

	  Saying Y will make the kernel somewhat larger and slower. However,
	  if you disable kmemtrace at run-time or boot-time, the performance
	  impact is minimal (depending on the arch the kernel is built for).

	  If unsure, say N.

287 288 289 290 291 292 293 294 295 296 297
config WORKQUEUE_TRACER
	bool "Trace workqueues"
	select TRACING
	help
	  The workqueue tracer provides some statistical informations
          about each cpu workqueue thread such as the number of the
          works inserted and executed since their creation. It can help
          to evaluate the amount of work each of them have to perform.
          For example it can help a developer to decide whether he should
          choose a per cpu workqueue instead of a singlethreaded one.

298

299 300
config DYNAMIC_FTRACE
	bool "enable/disable ftrace tracepoints dynamically"
301
	depends on FUNCTION_TRACER
302
	depends on HAVE_DYNAMIC_FTRACE
303
	depends on DEBUG_KERNEL
304 305 306 307 308 309 310
	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.

311
	 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but otherwise
312 313 314 315 316 317
	 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 已提交
318

319 320 321 322 323
config FTRACE_MCOUNT_RECORD
	def_bool y
	depends on DYNAMIC_FTRACE
	depends on HAVE_FTRACE_MCOUNT_RECORD

S
Steven Rostedt 已提交
324 325 326 327 328
config FTRACE_SELFTEST
	bool

config FTRACE_STARTUP_TEST
	bool "Perform a startup test on ftrace"
329
	depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER
S
Steven Rostedt 已提交
330 331 332 333 334 335
	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 已提交
336

337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359
config MMIOTRACE
	bool "Memory mapped IO tracing"
	depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI
	select TRACING
	help
	  Mmiotrace traces Memory Mapped I/O access and is meant for
	  debugging and reverse engineering. It is called from the ioremap
	  implementation and works via page faults. Tracing is disabled by
	  default and can be enabled at run-time.

	  See Documentation/tracers/mmiotrace.txt.
	  If you are not helping to develop drivers, say N.

config MMIOTRACE_TEST
	tristate "Test module for mmiotrace"
	depends on MMIOTRACE && m
	help
	  This is a dumb module for testing mmiotrace. It is very dangerous
	  as it will write garbage to IO memory starting at a given address.
	  However, it should be safe to use on e.g. unused portion of VRAM.

	  Say N, unless you absolutely know what you are doing.

P
Peter Zijlstra 已提交
360
endmenu