Commit | Line | Data |
---|---|---|
16444a8a | 1 | # |
606576ce SR |
2 | # Architectures that offer an FUNCTION_TRACER implementation should |
3 | # select HAVE_FUNCTION_TRACER: | |
16444a8a | 4 | # |
2a3a4f66 | 5 | |
8d26487f TE |
6 | config USER_STACKTRACE_SUPPORT |
7 | bool | |
8 | ||
2a3a4f66 FW |
9 | config NOP_TRACER |
10 | bool | |
11 | ||
78d904b4 SR |
12 | config HAVE_FTRACE_NMI_ENTER |
13 | bool | |
555f386c | 14 | help |
40892367 | 15 | See Documentation/trace/ftrace-design.txt |
78d904b4 | 16 | |
606576ce | 17 | config HAVE_FUNCTION_TRACER |
16444a8a | 18 | bool |
555f386c | 19 | help |
40892367 | 20 | See Documentation/trace/ftrace-design.txt |
bc0c38d1 | 21 | |
fb52607a | 22 | config HAVE_FUNCTION_GRAPH_TRACER |
15e6cb36 | 23 | bool |
555f386c | 24 | help |
40892367 | 25 | See Documentation/trace/ftrace-design.txt |
15e6cb36 | 26 | |
71e308a2 SR |
27 | config HAVE_FUNCTION_GRAPH_FP_TEST |
28 | bool | |
29 | help | |
03688970 | 30 | See Documentation/trace/ftrace-design.txt |
71e308a2 | 31 | |
60a7ecf4 SR |
32 | config HAVE_FUNCTION_TRACE_MCOUNT_TEST |
33 | bool | |
34 | help | |
40892367 | 35 | See Documentation/trace/ftrace-design.txt |
60a7ecf4 | 36 | |
677aa9f7 SR |
37 | config HAVE_DYNAMIC_FTRACE |
38 | bool | |
555f386c | 39 | help |
40892367 | 40 | See Documentation/trace/ftrace-design.txt |
677aa9f7 | 41 | |
06aeaaea MH |
42 | config HAVE_DYNAMIC_FTRACE_WITH_REGS |
43 | bool | |
44 | ||
8da3821b SR |
45 | config HAVE_FTRACE_MCOUNT_RECORD |
46 | bool | |
555f386c | 47 | help |
40892367 | 48 | See Documentation/trace/ftrace-design.txt |
8da3821b | 49 | |
66700001 | 50 | config HAVE_SYSCALL_TRACEPOINTS |
ee08c6ec | 51 | bool |
555f386c | 52 | help |
40892367 | 53 | See Documentation/trace/ftrace-design.txt |
ee08c6ec | 54 | |
a2546fae SR |
55 | config HAVE_FENTRY |
56 | bool | |
57 | help | |
58 | Arch supports the gcc options -pg with -mfentry | |
59 | ||
cf4db259 | 60 | config HAVE_C_RECORDMCOUNT |
72441cb1 SR |
61 | bool |
62 | help | |
63 | C version of recordmcount available? | |
64 | ||
352ad25a SR |
65 | config TRACER_MAX_TRACE |
66 | bool | |
67 | ||
ea632e9f JT |
68 | config TRACE_CLOCK |
69 | bool | |
70 | ||
7a8e76a3 SR |
71 | config RING_BUFFER |
72 | bool | |
ea632e9f | 73 | select TRACE_CLOCK |
7a8e76a3 | 74 | |
78d904b4 SR |
75 | config FTRACE_NMI_ENTER |
76 | bool | |
77 | depends on HAVE_FTRACE_NMI_ENTER | |
78 | default y | |
79 | ||
5f77a88b | 80 | config EVENT_TRACING |
b11c53e1 Z |
81 | select CONTEXT_SWITCH_TRACER |
82 | bool | |
83 | ||
25e41933 TR |
84 | config EVENT_POWER_TRACING_DEPRECATED |
85 | depends on EVENT_TRACING | |
86 | bool "Deprecated power event trace API, to be removed" | |
87 | default y | |
88 | help | |
89 | Provides old power event types: | |
90 | C-state/idle accounting events: | |
91 | power:power_start | |
92 | power:power_end | |
93 | and old cpufreq accounting event: | |
94 | power:power_frequency | |
95 | This is for userspace compatibility | |
96 | and will vanish after 5 kernel iterations, | |
f629299b | 97 | namely 3.1. |
25e41933 | 98 | |
b11c53e1 | 99 | config CONTEXT_SWITCH_TRACER |
5f77a88b TZ |
100 | bool |
101 | ||
85bac32c SR |
102 | config RING_BUFFER_ALLOW_SWAP |
103 | bool | |
104 | help | |
105 | Allow the use of ring_buffer_swap_cpu. | |
106 | Adds a very slight overhead to tracing when enabled. | |
107 | ||
5e0a0939 SR |
108 | # All tracer options should select GENERIC_TRACER. For those options that are |
109 | # enabled by all tracers (context switch and event tracer) they select TRACING. | |
110 | # This allows those options to appear when no other tracer is selected. But the | |
111 | # options do not appear when something else selects it. We need the two options | |
112 | # GENERIC_TRACER and TRACING to avoid circular dependencies to accomplish the | |
40892367 | 113 | # hiding of the automatic options. |
5e0a0939 | 114 | |
bc0c38d1 SR |
115 | config TRACING |
116 | bool | |
117 | select DEBUG_FS | |
7a8e76a3 | 118 | select RING_BUFFER |
c2c80529 | 119 | select STACKTRACE if STACKTRACE_SUPPORT |
5f87f112 | 120 | select TRACEPOINTS |
f3384b28 | 121 | select NOP_TRACER |
769b0441 | 122 | select BINARY_PRINTF |
5f77a88b | 123 | select EVENT_TRACING |
ea632e9f | 124 | select TRACE_CLOCK |
0d5c6e1c | 125 | select IRQ_WORK |
bc0c38d1 | 126 | |
5e0a0939 SR |
127 | config GENERIC_TRACER |
128 | bool | |
129 | select TRACING | |
130 | ||
40ada30f IM |
131 | # |
132 | # Minimum requirements an architecture has to meet for us to | |
133 | # be able to offer generic tracing facilities: | |
134 | # | |
135 | config TRACING_SUPPORT | |
136 | bool | |
45b95608 AV |
137 | # PPC32 has no irqflags tracing support, but it can use most of the |
138 | # tracers anyway, they were tested to build and work. Note that new | |
139 | # exceptions to this list aren't welcomed, better implement the | |
140 | # irqflags tracing for your architecture. | |
141 | depends on TRACE_IRQFLAGS_SUPPORT || PPC32 | |
40ada30f | 142 | depends on STACKTRACE_SUPPORT |
422d3c7a | 143 | default y |
40ada30f IM |
144 | |
145 | if TRACING_SUPPORT | |
146 | ||
4ed9f071 SR |
147 | menuconfig FTRACE |
148 | bool "Tracers" | |
65b77242 | 149 | default y if DEBUG_KERNEL |
4ed9f071 | 150 | help |
40892367 | 151 | Enable the kernel tracing infrastructure. |
4ed9f071 SR |
152 | |
153 | if FTRACE | |
17d80fd0 | 154 | |
606576ce | 155 | config FUNCTION_TRACER |
1b29b018 | 156 | bool "Kernel Function Tracer" |
606576ce | 157 | depends on HAVE_FUNCTION_TRACER |
4d7a077c | 158 | select KALLSYMS |
5e0a0939 | 159 | select GENERIC_TRACER |
35e8e302 | 160 | select CONTEXT_SWITCH_TRACER |
1b29b018 SR |
161 | help |
162 | Enable the kernel to trace every kernel function. This is done | |
163 | by using a compiler feature to insert a small, 5-byte No-Operation | |
40892367 | 164 | instruction at the beginning of every kernel function, which NOP |
1b29b018 SR |
165 | sequence is then dynamically patched into a tracer call when |
166 | tracing is enabled by the administrator. If it's runtime disabled | |
167 | (the bootup default), then the overhead of the instructions is very | |
168 | small and not measurable even in micro-benchmarks. | |
35e8e302 | 169 | |
fb52607a FW |
170 | config FUNCTION_GRAPH_TRACER |
171 | bool "Kernel Function Graph Tracer" | |
172 | depends on HAVE_FUNCTION_GRAPH_TRACER | |
15e6cb36 | 173 | depends on FUNCTION_TRACER |
eb4a0378 | 174 | depends on !X86_32 || !CC_OPTIMIZE_FOR_SIZE |
764f3b95 | 175 | default y |
15e6cb36 | 176 | help |
fb52607a FW |
177 | Enable the kernel to trace a function at both its return |
178 | and its entry. | |
692105b8 ML |
179 | Its first purpose is to trace the duration of functions and |
180 | draw a call graph for each thread with some information like | |
40892367 | 181 | the return value. This is done by setting the current return |
692105b8 | 182 | address on the current task structure into a stack of calls. |
15e6cb36 | 183 | |
bac429f0 | 184 | |
81d68a96 SR |
185 | config IRQSOFF_TRACER |
186 | bool "Interrupts-off Latency Tracer" | |
187 | default n | |
188 | depends on TRACE_IRQFLAGS_SUPPORT | |
592913ec | 189 | depends on !ARCH_USES_GETTIMEOFFSET |
81d68a96 | 190 | select TRACE_IRQFLAGS |
5e0a0939 | 191 | select GENERIC_TRACER |
81d68a96 | 192 | select TRACER_MAX_TRACE |
85bac32c | 193 | select RING_BUFFER_ALLOW_SWAP |
81d68a96 SR |
194 | help |
195 | This option measures the time spent in irqs-off critical | |
196 | sections, with microsecond accuracy. | |
197 | ||
198 | The default measurement method is a maximum search, which is | |
199 | disabled by default and can be runtime (re-)started | |
200 | via: | |
201 | ||
156f5a78 | 202 | echo 0 > /sys/kernel/debug/tracing/tracing_max_latency |
81d68a96 | 203 | |
40892367 | 204 | (Note that kernel size and overhead increase with this option |
6cd8a4bb SR |
205 | enabled. This option and the preempt-off timing option can be |
206 | used together or separately.) | |
207 | ||
208 | config PREEMPT_TRACER | |
209 | bool "Preemption-off Latency Tracer" | |
210 | default n | |
592913ec | 211 | depends on !ARCH_USES_GETTIMEOFFSET |
6cd8a4bb | 212 | depends on PREEMPT |
5e0a0939 | 213 | select GENERIC_TRACER |
6cd8a4bb | 214 | select TRACER_MAX_TRACE |
85bac32c | 215 | select RING_BUFFER_ALLOW_SWAP |
6cd8a4bb | 216 | help |
40892367 | 217 | This option measures the time spent in preemption-off critical |
6cd8a4bb SR |
218 | sections, with microsecond accuracy. |
219 | ||
220 | The default measurement method is a maximum search, which is | |
221 | disabled by default and can be runtime (re-)started | |
222 | via: | |
223 | ||
156f5a78 | 224 | echo 0 > /sys/kernel/debug/tracing/tracing_max_latency |
6cd8a4bb | 225 | |
40892367 | 226 | (Note that kernel size and overhead increase with this option |
6cd8a4bb SR |
227 | enabled. This option and the irqs-off timing option can be |
228 | used together or separately.) | |
229 | ||
352ad25a SR |
230 | config SCHED_TRACER |
231 | bool "Scheduling Latency Tracer" | |
5e0a0939 | 232 | select GENERIC_TRACER |
352ad25a SR |
233 | select CONTEXT_SWITCH_TRACER |
234 | select TRACER_MAX_TRACE | |
235 | help | |
236 | This tracer tracks the latency of the highest priority task | |
237 | to be scheduled in, starting from the point it has woken up. | |
238 | ||
897f17a6 SR |
239 | config ENABLE_DEFAULT_TRACERS |
240 | bool "Trace process context switches and events" | |
5e0a0939 | 241 | depends on !GENERIC_TRACER |
b77e38aa SR |
242 | select TRACING |
243 | help | |
40892367 | 244 | This tracer hooks to various trace points in the kernel, |
b77e38aa | 245 | allowing the user to pick and choose which trace point they |
897f17a6 | 246 | want to trace. It also includes the sched_switch tracer plugin. |
a7abe97f | 247 | |
ee08c6ec FW |
248 | config FTRACE_SYSCALLS |
249 | bool "Trace syscalls" | |
66700001 | 250 | depends on HAVE_SYSCALL_TRACEPOINTS |
5e0a0939 | 251 | select GENERIC_TRACER |
0ea1c415 | 252 | select KALLSYMS |
ee08c6ec FW |
253 | help |
254 | Basic tracer to catch the syscall entry and exit events. | |
255 | ||
debdd57f HT |
256 | config TRACER_SNAPSHOT |
257 | bool "Create a snapshot trace buffer" | |
258 | select TRACER_MAX_TRACE | |
259 | help | |
260 | Allow tracing users to take snapshot of the current buffer using the | |
261 | ftrace interface, e.g.: | |
262 | ||
263 | echo 1 > /sys/kernel/debug/tracing/snapshot | |
264 | cat snapshot | |
265 | ||
2ed84eeb | 266 | config TRACE_BRANCH_PROFILING |
9ae5b879 | 267 | bool |
5e0a0939 | 268 | select GENERIC_TRACER |
9ae5b879 SR |
269 | |
270 | choice | |
271 | prompt "Branch Profiling" | |
272 | default BRANCH_PROFILE_NONE | |
273 | help | |
274 | The branch profiling is a software profiler. It will add hooks | |
275 | into the C conditionals to test which path a branch takes. | |
276 | ||
277 | The likely/unlikely profiler only looks at the conditions that | |
278 | are annotated with a likely or unlikely macro. | |
279 | ||
40892367 | 280 | The "all branch" profiler will profile every if-statement in the |
9ae5b879 | 281 | kernel. This profiler will also enable the likely/unlikely |
40892367 | 282 | profiler. |
9ae5b879 | 283 | |
40892367 RD |
284 | Either of the above profilers adds a bit of overhead to the system. |
285 | If unsure, choose "No branch profiling". | |
9ae5b879 SR |
286 | |
287 | config BRANCH_PROFILE_NONE | |
288 | bool "No branch profiling" | |
289 | help | |
40892367 RD |
290 | No branch profiling. Branch profiling adds a bit of overhead. |
291 | Only enable it if you want to analyse the branching behavior. | |
292 | Otherwise keep it disabled. | |
9ae5b879 SR |
293 | |
294 | config PROFILE_ANNOTATED_BRANCHES | |
295 | bool "Trace likely/unlikely profiler" | |
296 | select TRACE_BRANCH_PROFILING | |
1f0d69a9 | 297 | help |
59bf8964 | 298 | This tracer profiles all likely and unlikely macros |
1f0d69a9 SR |
299 | in the kernel. It will display the results in: |
300 | ||
13e5befa | 301 | /sys/kernel/debug/tracing/trace_stat/branch_annotated |
1f0d69a9 | 302 | |
40892367 | 303 | Note: this will add a significant overhead; only turn this |
1f0d69a9 SR |
304 | on if you need to profile the system's use of these macros. |
305 | ||
2bcd521a SR |
306 | config PROFILE_ALL_BRANCHES |
307 | bool "Profile all if conditionals" | |
9ae5b879 | 308 | select TRACE_BRANCH_PROFILING |
2bcd521a SR |
309 | help |
310 | This tracer profiles all branch conditions. Every if () | |
311 | taken in the kernel is recorded whether it hit or miss. | |
312 | The results will be displayed in: | |
313 | ||
13e5befa | 314 | /sys/kernel/debug/tracing/trace_stat/branch_all |
2bcd521a | 315 | |
9ae5b879 SR |
316 | This option also enables the likely/unlikely profiler. |
317 | ||
2bcd521a SR |
318 | This configuration, when enabled, will impose a great overhead |
319 | on the system. This should only be enabled when the system | |
40892367 | 320 | is to be analyzed in much detail. |
9ae5b879 | 321 | endchoice |
2bcd521a | 322 | |
2ed84eeb | 323 | config TRACING_BRANCHES |
52f232cb SR |
324 | bool |
325 | help | |
326 | Selected by tracers that will trace the likely and unlikely | |
327 | conditions. This prevents the tracers themselves from being | |
328 | profiled. Profiling the tracing infrastructure can only happen | |
329 | when the likelys and unlikelys are not being traced. | |
330 | ||
2ed84eeb | 331 | config BRANCH_TRACER |
52f232cb | 332 | bool "Trace likely/unlikely instances" |
2ed84eeb SR |
333 | depends on TRACE_BRANCH_PROFILING |
334 | select TRACING_BRANCHES | |
52f232cb SR |
335 | help |
336 | This traces the events of likely and unlikely condition | |
337 | calls in the kernel. The difference between this and the | |
338 | "Trace likely/unlikely profiler" is that this is not a | |
339 | histogram of the callers, but actually places the calling | |
340 | events into a running trace buffer to see when and where the | |
341 | events happened, as well as their results. | |
342 | ||
343 | Say N if unsure. | |
344 | ||
e5a81b62 SR |
345 | config STACK_TRACER |
346 | bool "Trace max stack" | |
606576ce | 347 | depends on HAVE_FUNCTION_TRACER |
606576ce | 348 | select FUNCTION_TRACER |
e5a81b62 | 349 | select STACKTRACE |
4d7a077c | 350 | select KALLSYMS |
e5a81b62 | 351 | help |
4519d9e5 | 352 | This special tracer records the maximum stack footprint of the |
156f5a78 | 353 | kernel and displays it in /sys/kernel/debug/tracing/stack_trace. |
4519d9e5 IM |
354 | |
355 | This tracer works by hooking into every function call that the | |
356 | kernel executes, and keeping a maximum stack depth value and | |
f38f1d2a SR |
357 | stack-trace saved. If this is configured with DYNAMIC_FTRACE |
358 | then it will not have any overhead while the stack tracer | |
359 | is disabled. | |
360 | ||
361 | To enable the stack tracer on bootup, pass in 'stacktrace' | |
362 | on the kernel command line. | |
363 | ||
364 | The stack tracer can also be enabled or disabled via the | |
365 | sysctl kernel.stack_tracer_enabled | |
4519d9e5 IM |
366 | |
367 | Say N if unsure. | |
e5a81b62 | 368 | |
2db270a8 | 369 | config BLK_DEV_IO_TRACE |
40892367 | 370 | bool "Support for tracing block IO actions" |
2db270a8 | 371 | depends on SYSFS |
1dfba05d | 372 | depends on BLOCK |
2db270a8 FW |
373 | select RELAY |
374 | select DEBUG_FS | |
375 | select TRACEPOINTS | |
5e0a0939 | 376 | select GENERIC_TRACER |
2db270a8 FW |
377 | select STACKTRACE |
378 | help | |
379 | Say Y here if you want to be able to trace the block layer actions | |
380 | on a given queue. Tracing allows you to see any traffic happening | |
381 | on a block device queue. For more information (and the userspace | |
382 | support tools needed), fetch the blktrace tools from: | |
383 | ||
384 | git://git.kernel.dk/blktrace.git | |
385 | ||
386 | Tracing also is possible using the ftrace interface, e.g.: | |
387 | ||
388 | echo 1 > /sys/block/sda/sda1/trace/enable | |
389 | echo blk > /sys/kernel/debug/tracing/current_tracer | |
390 | cat /sys/kernel/debug/tracing/trace_pipe | |
391 | ||
392 | If unsure, say N. | |
36994e58 | 393 | |
77b44d1b | 394 | config KPROBE_EVENT |
413d37d1 | 395 | depends on KPROBES |
f850c30c | 396 | depends on HAVE_REGS_AND_STACK_ACCESS_API |
77b44d1b | 397 | bool "Enable kprobes-based dynamic events" |
413d37d1 | 398 | select TRACING |
8ab83f56 | 399 | select PROBE_EVENTS |
77b44d1b | 400 | default y |
413d37d1 | 401 | help |
40892367 RD |
402 | This allows the user to add tracing events (similar to tracepoints) |
403 | on the fly via the ftrace interface. See | |
404 | Documentation/trace/kprobetrace.txt for more details. | |
77b44d1b MH |
405 | |
406 | Those events can be inserted wherever kprobes can probe, and record | |
407 | various register and memory values. | |
408 | ||
40892367 RD |
409 | This option is also required by perf-probe subcommand of perf tools. |
410 | If you want to use perf tools, this option is strongly recommended. | |
413d37d1 | 411 | |
f3f096cf SD |
412 | config UPROBE_EVENT |
413 | bool "Enable uprobes-based dynamic events" | |
414 | depends on ARCH_SUPPORTS_UPROBES | |
415 | depends on MMU | |
416 | select UPROBES | |
417 | select PROBE_EVENTS | |
418 | select TRACING | |
419 | default n | |
420 | help | |
421 | This allows the user to add tracing events on top of userspace | |
422 | dynamic events (similar to tracepoints) on the fly via the trace | |
423 | events interface. Those events can be inserted wherever uprobes | |
424 | can probe, and record various registers. | |
425 | This option is required if you plan to use perf-probe subcommand | |
426 | of perf tools on user space applications. | |
427 | ||
8ab83f56 SD |
428 | config PROBE_EVENTS |
429 | def_bool n | |
430 | ||
3d083395 | 431 | config DYNAMIC_FTRACE |
db05021d | 432 | bool "enable/disable function tracing dynamically" |
606576ce | 433 | depends on FUNCTION_TRACER |
677aa9f7 | 434 | depends on HAVE_DYNAMIC_FTRACE |
3d083395 SR |
435 | default y |
436 | help | |
db05021d SR |
437 | This option will modify all the calls to function tracing |
438 | dynamically (will patch them out of the binary image and | |
439 | replace them with a No-Op instruction) on boot up. During | |
440 | compile time, a table is made of all the locations that ftrace | |
441 | can function trace, and this table is linked into the kernel | |
442 | image. When this is enabled, functions can be individually | |
443 | enabled, and the functions not enabled will not affect | |
444 | performance of the system. | |
445 | ||
446 | See the files in /sys/kernel/debug/tracing: | |
447 | available_filter_functions | |
448 | set_ftrace_filter | |
449 | set_ftrace_notrace | |
3d083395 | 450 | |
40892367 RD |
451 | This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but |
452 | otherwise has native performance as long as no tracing is active. | |
3d083395 | 453 | |
06aeaaea MH |
454 | config DYNAMIC_FTRACE_WITH_REGS |
455 | def_bool y | |
456 | depends on DYNAMIC_FTRACE | |
457 | depends on HAVE_DYNAMIC_FTRACE_WITH_REGS | |
458 | ||
bac429f0 SR |
459 | config FUNCTION_PROFILER |
460 | bool "Kernel function profiler" | |
493762fc | 461 | depends on FUNCTION_TRACER |
bac429f0 SR |
462 | default n |
463 | help | |
40892367 RD |
464 | This option enables the kernel function profiler. A file is created |
465 | in debugfs called function_profile_enabled which defaults to zero. | |
466 | When a 1 is echoed into this file profiling begins, and when a | |
467 | zero is entered, profiling stops. A "functions" file is created in | |
468 | the trace_stats directory; this file shows the list of functions that | |
469 | have been hit and their counters. | |
bac429f0 | 470 | |
40892367 | 471 | If in doubt, say N. |
bac429f0 | 472 | |
8da3821b SR |
473 | config FTRACE_MCOUNT_RECORD |
474 | def_bool y | |
475 | depends on DYNAMIC_FTRACE | |
476 | depends on HAVE_FTRACE_MCOUNT_RECORD | |
477 | ||
60a11774 SR |
478 | config FTRACE_SELFTEST |
479 | bool | |
480 | ||
481 | config FTRACE_STARTUP_TEST | |
482 | bool "Perform a startup test on ftrace" | |
5e0a0939 | 483 | depends on GENERIC_TRACER |
60a11774 SR |
484 | select FTRACE_SELFTEST |
485 | help | |
486 | This option performs a series of startup tests on ftrace. On bootup | |
487 | a series of tests are made to verify that the tracer is | |
488 | functioning properly. It will do tests on all the configured | |
489 | tracers of ftrace. | |
17d80fd0 | 490 | |
1f5a6b45 SR |
491 | config EVENT_TRACE_TEST_SYSCALLS |
492 | bool "Run selftest on syscall events" | |
493 | depends on FTRACE_STARTUP_TEST | |
494 | help | |
495 | This option will also enable testing every syscall event. | |
496 | It only enables the event and disables it and runs various loads | |
497 | with the event enabled. This adds a bit more time for kernel boot | |
498 | up since it runs this on every system call defined. | |
499 | ||
500 | TBD - enable a way to actually call the syscalls as we test their | |
501 | events | |
502 | ||
fe6f90e5 PP |
503 | config MMIOTRACE |
504 | bool "Memory mapped IO tracing" | |
40ada30f | 505 | depends on HAVE_MMIOTRACE_SUPPORT && PCI |
5e0a0939 | 506 | select GENERIC_TRACER |
fe6f90e5 PP |
507 | help |
508 | Mmiotrace traces Memory Mapped I/O access and is meant for | |
509 | debugging and reverse engineering. It is called from the ioremap | |
510 | implementation and works via page faults. Tracing is disabled by | |
511 | default and can be enabled at run-time. | |
512 | ||
4d1f4372 | 513 | See Documentation/trace/mmiotrace.txt. |
fe6f90e5 PP |
514 | If you are not helping to develop drivers, say N. |
515 | ||
516 | config MMIOTRACE_TEST | |
517 | tristate "Test module for mmiotrace" | |
518 | depends on MMIOTRACE && m | |
519 | help | |
520 | This is a dumb module for testing mmiotrace. It is very dangerous | |
521 | as it will write garbage to IO memory starting at a given address. | |
522 | However, it should be safe to use on e.g. unused portion of VRAM. | |
523 | ||
524 | Say N, unless you absolutely know what you are doing. | |
525 | ||
5092dbc9 SR |
526 | config RING_BUFFER_BENCHMARK |
527 | tristate "Ring buffer benchmark stress tester" | |
528 | depends on RING_BUFFER | |
529 | help | |
40892367 RD |
530 | This option creates a test to stress the ring buffer and benchmark it. |
531 | It creates its own ring buffer such that it will not interfere with | |
5092dbc9 SR |
532 | any other users of the ring buffer (such as ftrace). It then creates |
533 | a producer and consumer that will run for 10 seconds and sleep for | |
534 | 10 seconds. Each interval it will print out the number of events | |
535 | it recorded and give a rough estimate of how long each iteration took. | |
536 | ||
537 | It does not disable interrupts or raise its priority, so it may be | |
538 | affected by processes that are running. | |
539 | ||
40892367 | 540 | If unsure, say N. |
5092dbc9 | 541 | |
4ed9f071 | 542 | endif # FTRACE |
40ada30f IM |
543 | |
544 | endif # TRACING_SUPPORT | |
545 |