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