diff options
Diffstat (limited to 'kernel/trace/Kconfig')
-rw-r--r-- | kernel/trace/Kconfig | 123 |
1 files changed, 108 insertions, 15 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 504086ab4443..2246141bda4d 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig | |||
@@ -9,6 +9,9 @@ config USER_STACKTRACE_SUPPORT | |||
9 | config NOP_TRACER | 9 | config NOP_TRACER |
10 | bool | 10 | bool |
11 | 11 | ||
12 | config HAVE_FTRACE_NMI_ENTER | ||
13 | bool | ||
14 | |||
12 | config HAVE_FUNCTION_TRACER | 15 | config HAVE_FUNCTION_TRACER |
13 | bool | 16 | bool |
14 | 17 | ||
@@ -31,12 +34,20 @@ config HAVE_FTRACE_MCOUNT_RECORD | |||
31 | config HAVE_HW_BRANCH_TRACER | 34 | config HAVE_HW_BRANCH_TRACER |
32 | bool | 35 | bool |
33 | 36 | ||
37 | config HAVE_FTRACE_SYSCALLS | ||
38 | bool | ||
39 | |||
34 | config TRACER_MAX_TRACE | 40 | config TRACER_MAX_TRACE |
35 | bool | 41 | bool |
36 | 42 | ||
37 | config RING_BUFFER | 43 | config RING_BUFFER |
38 | bool | 44 | bool |
39 | 45 | ||
46 | config FTRACE_NMI_ENTER | ||
47 | bool | ||
48 | depends on HAVE_FTRACE_NMI_ENTER | ||
49 | default y | ||
50 | |||
40 | config TRACING | 51 | config TRACING |
41 | bool | 52 | bool |
42 | select DEBUG_FS | 53 | select DEBUG_FS |
@@ -44,13 +55,29 @@ config TRACING | |||
44 | select STACKTRACE if STACKTRACE_SUPPORT | 55 | select STACKTRACE if STACKTRACE_SUPPORT |
45 | select TRACEPOINTS | 56 | select TRACEPOINTS |
46 | select NOP_TRACER | 57 | select NOP_TRACER |
58 | select BINARY_PRINTF | ||
59 | |||
60 | # | ||
61 | # Minimum requirements an architecture has to meet for us to | ||
62 | # be able to offer generic tracing facilities: | ||
63 | # | ||
64 | config TRACING_SUPPORT | ||
65 | bool | ||
66 | # PPC32 has no irqflags tracing support, but it can use most of the | ||
67 | # tracers anyway, they were tested to build and work. Note that new | ||
68 | # exceptions to this list aren't welcomed, better implement the | ||
69 | # irqflags tracing for your architecture. | ||
70 | depends on TRACE_IRQFLAGS_SUPPORT || PPC32 | ||
71 | depends on STACKTRACE_SUPPORT | ||
72 | default y | ||
73 | |||
74 | if TRACING_SUPPORT | ||
47 | 75 | ||
48 | menu "Tracers" | 76 | menu "Tracers" |
49 | 77 | ||
50 | config FUNCTION_TRACER | 78 | config FUNCTION_TRACER |
51 | bool "Kernel Function Tracer" | 79 | bool "Kernel Function Tracer" |
52 | depends on HAVE_FUNCTION_TRACER | 80 | depends on HAVE_FUNCTION_TRACER |
53 | depends on DEBUG_KERNEL | ||
54 | select FRAME_POINTER | 81 | select FRAME_POINTER |
55 | select KALLSYMS | 82 | select KALLSYMS |
56 | select TRACING | 83 | select TRACING |
@@ -82,7 +109,6 @@ config IRQSOFF_TRACER | |||
82 | default n | 109 | default n |
83 | depends on TRACE_IRQFLAGS_SUPPORT | 110 | depends on TRACE_IRQFLAGS_SUPPORT |
84 | depends on GENERIC_TIME | 111 | depends on GENERIC_TIME |
85 | depends on DEBUG_KERNEL | ||
86 | select TRACE_IRQFLAGS | 112 | select TRACE_IRQFLAGS |
87 | select TRACING | 113 | select TRACING |
88 | select TRACER_MAX_TRACE | 114 | select TRACER_MAX_TRACE |
@@ -105,7 +131,6 @@ config PREEMPT_TRACER | |||
105 | default n | 131 | default n |
106 | depends on GENERIC_TIME | 132 | depends on GENERIC_TIME |
107 | depends on PREEMPT | 133 | depends on PREEMPT |
108 | depends on DEBUG_KERNEL | ||
109 | select TRACING | 134 | select TRACING |
110 | select TRACER_MAX_TRACE | 135 | select TRACER_MAX_TRACE |
111 | help | 136 | help |
@@ -126,13 +151,13 @@ config SYSPROF_TRACER | |||
126 | bool "Sysprof Tracer" | 151 | bool "Sysprof Tracer" |
127 | depends on X86 | 152 | depends on X86 |
128 | select TRACING | 153 | select TRACING |
154 | select CONTEXT_SWITCH_TRACER | ||
129 | help | 155 | help |
130 | This tracer provides the trace needed by the 'Sysprof' userspace | 156 | This tracer provides the trace needed by the 'Sysprof' userspace |
131 | tool. | 157 | tool. |
132 | 158 | ||
133 | config SCHED_TRACER | 159 | config SCHED_TRACER |
134 | bool "Scheduling Latency Tracer" | 160 | bool "Scheduling Latency Tracer" |
135 | depends on DEBUG_KERNEL | ||
136 | select TRACING | 161 | select TRACING |
137 | select CONTEXT_SWITCH_TRACER | 162 | select CONTEXT_SWITCH_TRACER |
138 | select TRACER_MAX_TRACE | 163 | select TRACER_MAX_TRACE |
@@ -142,16 +167,30 @@ config SCHED_TRACER | |||
142 | 167 | ||
143 | config CONTEXT_SWITCH_TRACER | 168 | config CONTEXT_SWITCH_TRACER |
144 | bool "Trace process context switches" | 169 | bool "Trace process context switches" |
145 | depends on DEBUG_KERNEL | ||
146 | select TRACING | 170 | select TRACING |
147 | select MARKERS | 171 | select MARKERS |
148 | help | 172 | help |
149 | This tracer gets called from the context switch and records | 173 | This tracer gets called from the context switch and records |
150 | all switching of tasks. | 174 | all switching of tasks. |
151 | 175 | ||
176 | config EVENT_TRACER | ||
177 | bool "Trace various events in the kernel" | ||
178 | select TRACING | ||
179 | help | ||
180 | This tracer hooks to various trace points in the kernel | ||
181 | allowing the user to pick and choose which trace point they | ||
182 | want to trace. | ||
183 | |||
184 | config FTRACE_SYSCALLS | ||
185 | bool "Trace syscalls" | ||
186 | depends on HAVE_FTRACE_SYSCALLS | ||
187 | select TRACING | ||
188 | select KALLSYMS | ||
189 | help | ||
190 | Basic tracer to catch the syscall entry and exit events. | ||
191 | |||
152 | config BOOT_TRACER | 192 | config BOOT_TRACER |
153 | bool "Trace boot initcalls" | 193 | bool "Trace boot initcalls" |
154 | depends on DEBUG_KERNEL | ||
155 | select TRACING | 194 | select TRACING |
156 | select CONTEXT_SWITCH_TRACER | 195 | select CONTEXT_SWITCH_TRACER |
157 | help | 196 | help |
@@ -164,13 +203,11 @@ config BOOT_TRACER | |||
164 | representation of the delays during initcalls - but the raw | 203 | representation of the delays during initcalls - but the raw |
165 | /debug/tracing/trace text output is readable too. | 204 | /debug/tracing/trace text output is readable too. |
166 | 205 | ||
167 | ( Note that tracing self tests can't be enabled if this tracer is | 206 | You must pass in ftrace=initcall to the kernel command line |
168 | selected, because the self-tests are an initcall as well and that | 207 | to enable this on bootup. |
169 | would invalidate the boot trace. ) | ||
170 | 208 | ||
171 | config TRACE_BRANCH_PROFILING | 209 | config TRACE_BRANCH_PROFILING |
172 | bool "Trace likely/unlikely profiler" | 210 | bool "Trace likely/unlikely profiler" |
173 | depends on DEBUG_KERNEL | ||
174 | select TRACING | 211 | select TRACING |
175 | help | 212 | help |
176 | This tracer profiles all the the likely and unlikely macros | 213 | This tracer profiles all the the likely and unlikely macros |
@@ -223,7 +260,6 @@ config BRANCH_TRACER | |||
223 | 260 | ||
224 | config POWER_TRACER | 261 | config POWER_TRACER |
225 | bool "Trace power consumption behavior" | 262 | bool "Trace power consumption behavior" |
226 | depends on DEBUG_KERNEL | ||
227 | depends on X86 | 263 | depends on X86 |
228 | select TRACING | 264 | select TRACING |
229 | help | 265 | help |
@@ -235,7 +271,6 @@ config POWER_TRACER | |||
235 | config STACK_TRACER | 271 | config STACK_TRACER |
236 | bool "Trace max stack" | 272 | bool "Trace max stack" |
237 | depends on HAVE_FUNCTION_TRACER | 273 | depends on HAVE_FUNCTION_TRACER |
238 | depends on DEBUG_KERNEL | ||
239 | select FUNCTION_TRACER | 274 | select FUNCTION_TRACER |
240 | select STACKTRACE | 275 | select STACKTRACE |
241 | select KALLSYMS | 276 | select KALLSYMS |
@@ -265,11 +300,66 @@ config HW_BRANCH_TRACER | |||
265 | This tracer records all branches on the system in a circular | 300 | This tracer records all branches on the system in a circular |
266 | buffer giving access to the last N branches for each cpu. | 301 | buffer giving access to the last N branches for each cpu. |
267 | 302 | ||
303 | config KMEMTRACE | ||
304 | bool "Trace SLAB allocations" | ||
305 | select TRACING | ||
306 | help | ||
307 | kmemtrace provides tracing for slab allocator functions, such as | ||
308 | kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected | ||
309 | data is then fed to the userspace application in order to analyse | ||
310 | allocation hotspots, internal fragmentation and so on, making it | ||
311 | possible to see how well an allocator performs, as well as debug | ||
312 | and profile kernel code. | ||
313 | |||
314 | This requires an userspace application to use. See | ||
315 | Documentation/vm/kmemtrace.txt for more information. | ||
316 | |||
317 | Saying Y will make the kernel somewhat larger and slower. However, | ||
318 | if you disable kmemtrace at run-time or boot-time, the performance | ||
319 | impact is minimal (depending on the arch the kernel is built for). | ||
320 | |||
321 | If unsure, say N. | ||
322 | |||
323 | config WORKQUEUE_TRACER | ||
324 | bool "Trace workqueues" | ||
325 | select TRACING | ||
326 | help | ||
327 | The workqueue tracer provides some statistical informations | ||
328 | about each cpu workqueue thread such as the number of the | ||
329 | works inserted and executed since their creation. It can help | ||
330 | to evaluate the amount of work each of them have to perform. | ||
331 | For example it can help a developer to decide whether he should | ||
332 | choose a per cpu workqueue instead of a singlethreaded one. | ||
333 | |||
334 | config BLK_DEV_IO_TRACE | ||
335 | bool "Support for tracing block io actions" | ||
336 | depends on SYSFS | ||
337 | depends on BLOCK | ||
338 | select RELAY | ||
339 | select DEBUG_FS | ||
340 | select TRACEPOINTS | ||
341 | select TRACING | ||
342 | select STACKTRACE | ||
343 | help | ||
344 | Say Y here if you want to be able to trace the block layer actions | ||
345 | on a given queue. Tracing allows you to see any traffic happening | ||
346 | on a block device queue. For more information (and the userspace | ||
347 | support tools needed), fetch the blktrace tools from: | ||
348 | |||
349 | git://git.kernel.dk/blktrace.git | ||
350 | |||
351 | Tracing also is possible using the ftrace interface, e.g.: | ||
352 | |||
353 | echo 1 > /sys/block/sda/sda1/trace/enable | ||
354 | echo blk > /sys/kernel/debug/tracing/current_tracer | ||
355 | cat /sys/kernel/debug/tracing/trace_pipe | ||
356 | |||
357 | If unsure, say N. | ||
358 | |||
268 | config DYNAMIC_FTRACE | 359 | config DYNAMIC_FTRACE |
269 | bool "enable/disable ftrace tracepoints dynamically" | 360 | bool "enable/disable ftrace tracepoints dynamically" |
270 | depends on FUNCTION_TRACER | 361 | depends on FUNCTION_TRACER |
271 | depends on HAVE_DYNAMIC_FTRACE | 362 | depends on HAVE_DYNAMIC_FTRACE |
272 | depends on DEBUG_KERNEL | ||
273 | default y | 363 | default y |
274 | help | 364 | help |
275 | This option will modify all the calls to ftrace dynamically | 365 | This option will modify all the calls to ftrace dynamically |
@@ -295,7 +385,7 @@ config FTRACE_SELFTEST | |||
295 | 385 | ||
296 | config FTRACE_STARTUP_TEST | 386 | config FTRACE_STARTUP_TEST |
297 | bool "Perform a startup test on ftrace" | 387 | bool "Perform a startup test on ftrace" |
298 | depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER | 388 | depends on TRACING |
299 | select FTRACE_SELFTEST | 389 | select FTRACE_SELFTEST |
300 | help | 390 | help |
301 | This option performs a series of startup tests on ftrace. On bootup | 391 | This option performs a series of startup tests on ftrace. On bootup |
@@ -305,7 +395,7 @@ config FTRACE_STARTUP_TEST | |||
305 | 395 | ||
306 | config MMIOTRACE | 396 | config MMIOTRACE |
307 | bool "Memory mapped IO tracing" | 397 | bool "Memory mapped IO tracing" |
308 | depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI | 398 | depends on HAVE_MMIOTRACE_SUPPORT && PCI |
309 | select TRACING | 399 | select TRACING |
310 | help | 400 | help |
311 | Mmiotrace traces Memory Mapped I/O access and is meant for | 401 | Mmiotrace traces Memory Mapped I/O access and is meant for |
@@ -327,3 +417,6 @@ config MMIOTRACE_TEST | |||
327 | Say N, unless you absolutely know what you are doing. | 417 | Say N, unless you absolutely know what you are doing. |
328 | 418 | ||
329 | endmenu | 419 | endmenu |
420 | |||
421 | endif # TRACING_SUPPORT | ||
422 | |||