Blame view
kernel/trace/Kconfig
14.5 KB
16444a8a4 ftrace: add basic... |
1 |
# |
606576ce8 ftrace: rename FT... |
2 3 |
# Architectures that offer an FUNCTION_TRACER implementation should # select HAVE_FUNCTION_TRACER: |
16444a8a4 ftrace: add basic... |
4 |
# |
2a3a4f669 tracing/ftrace: t... |
5 |
|
8d26487fd tracing/stack-tra... |
6 7 |
config USER_STACKTRACE_SUPPORT bool |
2a3a4f669 tracing/ftrace: t... |
8 9 |
config NOP_TRACER bool |
78d904b46 ring-buffer: add ... |
10 11 |
config HAVE_FTRACE_NMI_ENTER bool |
555f386c9 ftrace: document ... |
12 |
help |
40892367b tracing: Kconfig ... |
13 |
See Documentation/trace/ftrace-design.txt |
78d904b46 ring-buffer: add ... |
14 |
|
606576ce8 ftrace: rename FT... |
15 |
config HAVE_FUNCTION_TRACER |
16444a8a4 ftrace: add basic... |
16 |
bool |
555f386c9 ftrace: document ... |
17 |
help |
40892367b tracing: Kconfig ... |
18 |
See Documentation/trace/ftrace-design.txt |
bc0c38d13 ftrace: latency t... |
19 |
|
fb52607af tracing/function-... |
20 |
config HAVE_FUNCTION_GRAPH_TRACER |
15e6cb367 tracing: add a tr... |
21 |
bool |
555f386c9 ftrace: document ... |
22 |
help |
40892367b tracing: Kconfig ... |
23 |
See Documentation/trace/ftrace-design.txt |
15e6cb367 tracing: add a tr... |
24 |
|
71e308a23 function-graph: a... |
25 26 27 |
config HAVE_FUNCTION_GRAPH_FP_TEST bool help |
036889703 tracing/documenta... |
28 |
See Documentation/trace/ftrace-design.txt |
71e308a23 function-graph: a... |
29 |
|
60a7ecf42 ftrace: add quick... |
30 31 32 |
config HAVE_FUNCTION_TRACE_MCOUNT_TEST bool help |
40892367b tracing: Kconfig ... |
33 |
See Documentation/trace/ftrace-design.txt |
60a7ecf42 ftrace: add quick... |
34 |
|
677aa9f77 ftrace: add have ... |
35 36 |
config HAVE_DYNAMIC_FTRACE bool |
555f386c9 ftrace: document ... |
37 |
help |
40892367b tracing: Kconfig ... |
38 |
See Documentation/trace/ftrace-design.txt |
677aa9f77 ftrace: add have ... |
39 |
|
8da3821ba ftrace: create __... |
40 41 |
config HAVE_FTRACE_MCOUNT_RECORD bool |
555f386c9 ftrace: document ... |
42 |
help |
40892367b tracing: Kconfig ... |
43 |
See Documentation/trace/ftrace-design.txt |
8da3821ba ftrace: create __... |
44 |
|
667000011 tracing: Rename F... |
45 |
config HAVE_SYSCALL_TRACEPOINTS |
ee08c6ecc tracing/ftrace: s... |
46 |
bool |
555f386c9 ftrace: document ... |
47 |
help |
40892367b tracing: Kconfig ... |
48 |
See Documentation/trace/ftrace-design.txt |
ee08c6ecc tracing/ftrace: s... |
49 |
|
cf4db2597 ftrace: Rename co... |
50 |
config HAVE_C_RECORDMCOUNT |
72441cb1f ftrace/x86: Add s... |
51 52 53 |
bool help C version of recordmcount available? |
352ad25aa ftrace: tracer fo... |
54 55 |
config TRACER_MAX_TRACE bool |
7a8e76a38 tracing: unified ... |
56 57 |
config RING_BUFFER bool |
78d904b46 ring-buffer: add ... |
58 59 60 61 |
config FTRACE_NMI_ENTER bool depends on HAVE_FTRACE_NMI_ENTER default y |
5f77a88b3 tracing/infrastru... |
62 |
config EVENT_TRACING |
b11c53e12 ftrace: Add task_... |
63 64 |
select CONTEXT_SWITCH_TRACER bool |
25e41933b perf: Clean up po... |
65 66 67 68 69 70 71 72 73 74 75 76 77 |
config EVENT_POWER_TRACING_DEPRECATED depends on EVENT_TRACING bool "Deprecated power event trace API, to be removed" default y help Provides old power event types: C-state/idle accounting events: power:power_start power:power_end and old cpufreq accounting event: power:power_frequency This is for userspace compatibility and will vanish after 5 kernel iterations, |
f629299b5 trace events: Upd... |
78 |
namely 3.1. |
25e41933b perf: Clean up po... |
79 |
|
b11c53e12 ftrace: Add task_... |
80 |
config CONTEXT_SWITCH_TRACER |
5f77a88b3 tracing/infrastru... |
81 |
bool |
85bac32c4 ring-buffer: only... |
82 83 84 85 86 |
config RING_BUFFER_ALLOW_SWAP bool help Allow the use of ring_buffer_swap_cpu. Adds a very slight overhead to tracing when enabled. |
5e0a09391 tracing: fix conf... |
87 88 89 90 91 |
# All tracer options should select GENERIC_TRACER. For those options that are # enabled by all tracers (context switch and event tracer) they select TRACING. # This allows those options to appear when no other tracer is selected. But the # options do not appear when something else selects it. We need the two options # GENERIC_TRACER and TRACING to avoid circular dependencies to accomplish the |
40892367b tracing: Kconfig ... |
92 |
# hiding of the automatic options. |
5e0a09391 tracing: fix conf... |
93 |
|
bc0c38d13 ftrace: latency t... |
94 95 96 |
config TRACING bool select DEBUG_FS |
7a8e76a38 tracing: unified ... |
97 |
select RING_BUFFER |
c2c805294 tracing, alpha: u... |
98 |
select STACKTRACE if STACKTRACE_SUPPORT |
5f87f1121 tracing: clean up... |
99 |
select TRACEPOINTS |
f3384b28a ftrace: fix trace... |
100 |
select NOP_TRACER |
769b0441f tracing/core: dro... |
101 |
select BINARY_PRINTF |
5f77a88b3 tracing/infrastru... |
102 |
select EVENT_TRACING |
bc0c38d13 ftrace: latency t... |
103 |
|
5e0a09391 tracing: fix conf... |
104 105 106 |
config GENERIC_TRACER bool select TRACING |
40ada30f9 tracing: clean up... |
107 108 109 110 111 112 |
# # Minimum requirements an architecture has to meet for us to # be able to offer generic tracing facilities: # config TRACING_SUPPORT bool |
45b956089 tracing: Fix TRAC... |
113 114 115 116 117 |
# PPC32 has no irqflags tracing support, but it can use most of the # tracers anyway, they were tested to build and work. Note that new # exceptions to this list aren't welcomed, better implement the # irqflags tracing for your architecture. depends on TRACE_IRQFLAGS_SUPPORT || PPC32 |
40ada30f9 tracing: clean up... |
118 |
depends on STACKTRACE_SUPPORT |
422d3c7a5 tracing: current ... |
119 |
default y |
40ada30f9 tracing: clean up... |
120 121 |
if TRACING_SUPPORT |
4ed9f0716 tracing: create m... |
122 123 |
menuconfig FTRACE bool "Tracers" |
65b772420 tracing: have men... |
124 |
default y if DEBUG_KERNEL |
4ed9f0716 tracing: create m... |
125 |
help |
40892367b tracing: Kconfig ... |
126 |
Enable the kernel tracing infrastructure. |
4ed9f0716 tracing: create m... |
127 128 |
if FTRACE |
17d80fd07 tracing: create t... |
129 |
|
606576ce8 ftrace: rename FT... |
130 |
config FUNCTION_TRACER |
1b29b0188 ftrace: function ... |
131 |
bool "Kernel Function Tracer" |
606576ce8 ftrace: rename FT... |
132 |
depends on HAVE_FUNCTION_TRACER |
d20ac2528 ftrace: Build wit... |
133 |
select FRAME_POINTER if !ARM_UNWIND && !S390 && !MICROBLAZE |
4d7a077c0 tracing: have fun... |
134 |
select KALLSYMS |
5e0a09391 tracing: fix conf... |
135 |
select GENERIC_TRACER |
35e8e302e ftrace: add traci... |
136 |
select CONTEXT_SWITCH_TRACER |
1b29b0188 ftrace: function ... |
137 138 139 |
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 |
40892367b tracing: Kconfig ... |
140 |
instruction at the beginning of every kernel function, which NOP |
1b29b0188 ftrace: function ... |
141 142 143 144 |
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. |
35e8e302e ftrace: add traci... |
145 |
|
fb52607af tracing/function-... |
146 147 148 |
config FUNCTION_GRAPH_TRACER bool "Kernel Function Graph Tracer" depends on HAVE_FUNCTION_GRAPH_TRACER |
15e6cb367 tracing: add a tr... |
149 |
depends on FUNCTION_TRACER |
eb4a03780 function-graph: d... |
150 |
depends on !X86_32 || !CC_OPTIMIZE_FOR_SIZE |
764f3b951 tracing/function-... |
151 |
default y |
15e6cb367 tracing: add a tr... |
152 |
help |
fb52607af tracing/function-... |
153 154 |
Enable the kernel to trace a function at both its return and its entry. |
692105b8a trivial: fix typo... |
155 156 |
Its first purpose is to trace the duration of functions and draw a call graph for each thread with some information like |
40892367b tracing: Kconfig ... |
157 |
the return value. This is done by setting the current return |
692105b8a trivial: fix typo... |
158 |
address on the current task structure into a stack of calls. |
15e6cb367 tracing: add a tr... |
159 |
|
bac429f03 tracing: add func... |
160 |
|
81d68a96a ftrace: trace irq... |
161 162 163 164 |
config IRQSOFF_TRACER bool "Interrupts-off Latency Tracer" default n depends on TRACE_IRQFLAGS_SUPPORT |
592913ecb time: Kill off CO... |
165 |
depends on !ARCH_USES_GETTIMEOFFSET |
81d68a96a ftrace: trace irq... |
166 |
select TRACE_IRQFLAGS |
5e0a09391 tracing: fix conf... |
167 |
select GENERIC_TRACER |
81d68a96a ftrace: trace irq... |
168 |
select TRACER_MAX_TRACE |
85bac32c4 ring-buffer: only... |
169 |
select RING_BUFFER_ALLOW_SWAP |
81d68a96a ftrace: trace irq... |
170 171 172 173 174 175 176 |
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: |
156f5a780 debugfs: Fix term... |
177 |
echo 0 > /sys/kernel/debug/tracing/tracing_max_latency |
81d68a96a ftrace: trace irq... |
178 |
|
40892367b tracing: Kconfig ... |
179 |
(Note that kernel size and overhead increase with this option |
6cd8a4bb2 ftrace: trace pre... |
180 181 182 183 184 185 |
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 |
592913ecb time: Kill off CO... |
186 |
depends on !ARCH_USES_GETTIMEOFFSET |
6cd8a4bb2 ftrace: trace pre... |
187 |
depends on PREEMPT |
5e0a09391 tracing: fix conf... |
188 |
select GENERIC_TRACER |
6cd8a4bb2 ftrace: trace pre... |
189 |
select TRACER_MAX_TRACE |
85bac32c4 ring-buffer: only... |
190 |
select RING_BUFFER_ALLOW_SWAP |
6cd8a4bb2 ftrace: trace pre... |
191 |
help |
40892367b tracing: Kconfig ... |
192 |
This option measures the time spent in preemption-off critical |
6cd8a4bb2 ftrace: trace pre... |
193 194 195 196 197 |
sections, with microsecond accuracy. The default measurement method is a maximum search, which is disabled by default and can be runtime (re-)started via: |
156f5a780 debugfs: Fix term... |
198 |
echo 0 > /sys/kernel/debug/tracing/tracing_max_latency |
6cd8a4bb2 ftrace: trace pre... |
199 |
|
40892367b tracing: Kconfig ... |
200 |
(Note that kernel size and overhead increase with this option |
6cd8a4bb2 ftrace: trace pre... |
201 202 |
enabled. This option and the irqs-off timing option can be used together or separately.) |
352ad25aa ftrace: tracer fo... |
203 204 |
config SCHED_TRACER bool "Scheduling Latency Tracer" |
5e0a09391 tracing: fix conf... |
205 |
select GENERIC_TRACER |
352ad25aa ftrace: tracer fo... |
206 207 208 209 210 |
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. |
897f17a65 tracing: combine ... |
211 212 |
config ENABLE_DEFAULT_TRACERS bool "Trace process context switches and events" |
5e0a09391 tracing: fix conf... |
213 |
depends on !GENERIC_TRACER |
b77e38aa2 tracing: add even... |
214 215 |
select TRACING help |
40892367b tracing: Kconfig ... |
216 |
This tracer hooks to various trace points in the kernel, |
b77e38aa2 tracing: add even... |
217 |
allowing the user to pick and choose which trace point they |
897f17a65 tracing: combine ... |
218 |
want to trace. It also includes the sched_switch tracer plugin. |
a7abe97fd tracing: rename E... |
219 |
|
ee08c6ecc tracing/ftrace: s... |
220 221 |
config FTRACE_SYSCALLS bool "Trace syscalls" |
667000011 tracing: Rename F... |
222 |
depends on HAVE_SYSCALL_TRACEPOINTS |
5e0a09391 tracing: fix conf... |
223 |
select GENERIC_TRACER |
0ea1c4156 tracing/syscalls:... |
224 |
select KALLSYMS |
ee08c6ecc tracing/ftrace: s... |
225 226 |
help Basic tracer to catch the syscall entry and exit events. |
2ed84eeb8 trace: rename unl... |
227 |
config TRACE_BRANCH_PROFILING |
9ae5b8790 tracing: change b... |
228 |
bool |
5e0a09391 tracing: fix conf... |
229 |
select GENERIC_TRACER |
9ae5b8790 tracing: change b... |
230 231 232 233 234 235 236 237 238 239 |
choice prompt "Branch Profiling" default BRANCH_PROFILE_NONE help The branch profiling is a software profiler. It will add hooks into the C conditionals to test which path a branch takes. The likely/unlikely profiler only looks at the conditions that are annotated with a likely or unlikely macro. |
40892367b tracing: Kconfig ... |
240 |
The "all branch" profiler will profile every if-statement in the |
9ae5b8790 tracing: change b... |
241 |
kernel. This profiler will also enable the likely/unlikely |
40892367b tracing: Kconfig ... |
242 |
profiler. |
9ae5b8790 tracing: change b... |
243 |
|
40892367b tracing: Kconfig ... |
244 245 |
Either of the above profilers adds a bit of overhead to the system. If unsure, choose "No branch profiling". |
9ae5b8790 tracing: change b... |
246 247 248 249 |
config BRANCH_PROFILE_NONE bool "No branch profiling" help |
40892367b tracing: Kconfig ... |
250 251 252 |
No branch profiling. Branch profiling adds a bit of overhead. Only enable it if you want to analyse the branching behavior. Otherwise keep it disabled. |
9ae5b8790 tracing: change b... |
253 254 255 256 |
config PROFILE_ANNOTATED_BRANCHES bool "Trace likely/unlikely profiler" select TRACE_BRANCH_PROFILING |
1f0d69a9f tracing: profile ... |
257 258 259 |
help This tracer profiles all the the likely and unlikely macros in the kernel. It will display the results in: |
13e5befad trace, documentat... |
260 |
/sys/kernel/debug/tracing/trace_stat/branch_annotated |
1f0d69a9f tracing: profile ... |
261 |
|
40892367b tracing: Kconfig ... |
262 |
Note: this will add a significant overhead; only turn this |
1f0d69a9f tracing: profile ... |
263 |
on if you need to profile the system's use of these macros. |
2bcd521a6 trace: profile al... |
264 265 |
config PROFILE_ALL_BRANCHES bool "Profile all if conditionals" |
9ae5b8790 tracing: change b... |
266 |
select TRACE_BRANCH_PROFILING |
2bcd521a6 trace: profile al... |
267 268 269 270 |
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: |
13e5befad trace, documentat... |
271 |
/sys/kernel/debug/tracing/trace_stat/branch_all |
2bcd521a6 trace: profile al... |
272 |
|
9ae5b8790 tracing: change b... |
273 |
This option also enables the likely/unlikely profiler. |
2bcd521a6 trace: profile al... |
274 275 |
This configuration, when enabled, will impose a great overhead on the system. This should only be enabled when the system |
40892367b tracing: Kconfig ... |
276 |
is to be analyzed in much detail. |
9ae5b8790 tracing: change b... |
277 |
endchoice |
2bcd521a6 trace: profile al... |
278 |
|
2ed84eeb8 trace: rename unl... |
279 |
config TRACING_BRANCHES |
52f232cb7 tracing: likely/u... |
280 281 282 283 284 285 |
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. |
2ed84eeb8 trace: rename unl... |
286 |
config BRANCH_TRACER |
52f232cb7 tracing: likely/u... |
287 |
bool "Trace likely/unlikely instances" |
2ed84eeb8 trace: rename unl... |
288 289 |
depends on TRACE_BRANCH_PROFILING select TRACING_BRANCHES |
52f232cb7 tracing: likely/u... |
290 291 292 293 294 295 296 297 298 |
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. |
e5a81b629 ftrace: add stack... |
299 300 |
config STACK_TRACER bool "Trace max stack" |
606576ce8 ftrace: rename FT... |
301 |
depends on HAVE_FUNCTION_TRACER |
606576ce8 ftrace: rename FT... |
302 |
select FUNCTION_TRACER |
e5a81b629 ftrace: add stack... |
303 |
select STACKTRACE |
4d7a077c0 tracing: have fun... |
304 |
select KALLSYMS |
e5a81b629 ftrace: add stack... |
305 |
help |
4519d9e54 tracing/stacktrac... |
306 |
This special tracer records the maximum stack footprint of the |
156f5a780 debugfs: Fix term... |
307 |
kernel and displays it in /sys/kernel/debug/tracing/stack_trace. |
4519d9e54 tracing/stacktrac... |
308 309 310 |
This tracer works by hooking into every function call that the kernel executes, and keeping a maximum stack depth value and |
f38f1d2aa trace: add a way ... |
311 312 313 314 315 316 317 318 319 |
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 |
4519d9e54 tracing/stacktrac... |
320 321 |
Say N if unsure. |
e5a81b629 ftrace: add stack... |
322 |
|
2db270a80 tracing/blktrace:... |
323 |
config BLK_DEV_IO_TRACE |
40892367b tracing: Kconfig ... |
324 |
bool "Support for tracing block IO actions" |
2db270a80 tracing/blktrace:... |
325 |
depends on SYSFS |
1dfba05d0 tracing/blktrace:... |
326 |
depends on BLOCK |
2db270a80 tracing/blktrace:... |
327 328 329 |
select RELAY select DEBUG_FS select TRACEPOINTS |
5e0a09391 tracing: fix conf... |
330 |
select GENERIC_TRACER |
2db270a80 tracing/blktrace:... |
331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 |
select STACKTRACE help Say Y here if you want to be able to trace the block layer actions on a given queue. Tracing allows you to see any traffic happening on a block device queue. For more information (and the userspace support tools needed), fetch the blktrace tools from: git://git.kernel.dk/blktrace.git Tracing also is possible using the ftrace interface, e.g.: echo 1 > /sys/block/sda/sda1/trace/enable echo blk > /sys/kernel/debug/tracing/current_tracer cat /sys/kernel/debug/tracing/trace_pipe If unsure, say N. |
36994e58a tracing/kmemtrace... |
347 |
|
77b44d1b7 tracing/kprobes: ... |
348 |
config KPROBE_EVENT |
413d37d1e tracing: Add kpro... |
349 |
depends on KPROBES |
f850c30c8 tracing/kprobes: ... |
350 |
depends on HAVE_REGS_AND_STACK_ACCESS_API |
77b44d1b7 tracing/kprobes: ... |
351 |
bool "Enable kprobes-based dynamic events" |
413d37d1e tracing: Add kpro... |
352 |
select TRACING |
77b44d1b7 tracing/kprobes: ... |
353 |
default y |
413d37d1e tracing: Add kpro... |
354 |
help |
40892367b tracing: Kconfig ... |
355 356 357 |
This allows the user to add tracing events (similar to tracepoints) on the fly via the ftrace interface. See Documentation/trace/kprobetrace.txt for more details. |
77b44d1b7 tracing/kprobes: ... |
358 359 360 |
Those events can be inserted wherever kprobes can probe, and record various register and memory values. |
40892367b tracing: Kconfig ... |
361 362 |
This option is also required by perf-probe subcommand of perf tools. If you want to use perf tools, this option is strongly recommended. |
413d37d1e tracing: Add kpro... |
363 |
|
3d0833953 ftrace: dynamic e... |
364 365 |
config DYNAMIC_FTRACE bool "enable/disable ftrace tracepoints dynamically" |
606576ce8 ftrace: rename FT... |
366 |
depends on FUNCTION_TRACER |
677aa9f77 ftrace: add have ... |
367 |
depends on HAVE_DYNAMIC_FTRACE |
3d0833953 ftrace: dynamic e... |
368 369 |
default y help |
40892367b tracing: Kconfig ... |
370 371 372 373 |
This option will modify all the calls to ftrace dynamically (will patch them out of the binary image and replace them with a No-Op instruction) as they are called. A table is created to dynamically enable them again. |
3d0833953 ftrace: dynamic e... |
374 |
|
40892367b tracing: Kconfig ... |
375 376 |
This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but otherwise has native performance as long as no tracing is active. |
3d0833953 ftrace: dynamic e... |
377 |
|
40892367b tracing: Kconfig ... |
378 379 380 381 |
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. |
60a11774b ftrace: add self-... |
382 |
|
bac429f03 tracing: add func... |
383 384 |
config FUNCTION_PROFILER bool "Kernel function profiler" |
493762fc5 tracing: move fun... |
385 |
depends on FUNCTION_TRACER |
bac429f03 tracing: add func... |
386 387 |
default n help |
40892367b tracing: Kconfig ... |
388 389 390 391 392 393 |
This option enables the kernel function profiler. A file is created in debugfs called function_profile_enabled which defaults to zero. When a 1 is echoed into this file profiling begins, and when a zero is entered, profiling stops. A "functions" file is created in the trace_stats directory; this file shows the list of functions that have been hit and their counters. |
bac429f03 tracing: add func... |
394 |
|
40892367b tracing: Kconfig ... |
395 |
If in doubt, say N. |
bac429f03 tracing: add func... |
396 |
|
8da3821ba ftrace: create __... |
397 398 399 400 |
config FTRACE_MCOUNT_RECORD def_bool y depends on DYNAMIC_FTRACE depends on HAVE_FTRACE_MCOUNT_RECORD |
60a11774b ftrace: add self-... |
401 402 403 404 405 |
config FTRACE_SELFTEST bool config FTRACE_STARTUP_TEST bool "Perform a startup test on ftrace" |
5e0a09391 tracing: fix conf... |
406 |
depends on GENERIC_TRACER |
60a11774b ftrace: add self-... |
407 408 409 410 411 412 |
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. |
17d80fd07 tracing: create t... |
413 |
|
1f5a6b454 tracing: make tes... |
414 415 416 417 418 419 420 421 422 423 424 |
config EVENT_TRACE_TEST_SYSCALLS bool "Run selftest on syscall events" depends on FTRACE_STARTUP_TEST help This option will also enable testing every syscall event. It only enables the event and disables it and runs various loads with the event enabled. This adds a bit more time for kernel boot up since it runs this on every system call defined. TBD - enable a way to actually call the syscalls as we test their events |
fe6f90e57 trace: mmiotrace ... |
425 426 |
config MMIOTRACE bool "Memory mapped IO tracing" |
40ada30f9 tracing: clean up... |
427 |
depends on HAVE_MMIOTRACE_SUPPORT && PCI |
5e0a09391 tracing: fix conf... |
428 |
select GENERIC_TRACER |
fe6f90e57 trace: mmiotrace ... |
429 430 431 432 433 |
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. |
4d1f4372d tracing: fix docu... |
434 |
See Documentation/trace/mmiotrace.txt. |
fe6f90e57 trace: mmiotrace ... |
435 436 437 438 439 440 441 442 443 444 445 |
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. |
5092dbc96 ring-buffer: add ... |
446 447 448 449 |
config RING_BUFFER_BENCHMARK tristate "Ring buffer benchmark stress tester" depends on RING_BUFFER help |
40892367b tracing: Kconfig ... |
450 451 |
This option creates a test to stress the ring buffer and benchmark it. It creates its own ring buffer such that it will not interfere with |
5092dbc96 ring-buffer: add ... |
452 453 454 455 456 457 458 |
any other users of the ring buffer (such as ftrace). It then creates a producer and consumer that will run for 10 seconds and sleep for 10 seconds. Each interval it will print out the number of events it recorded and give a rough estimate of how long each iteration took. It does not disable interrupts or raise its priority, so it may be affected by processes that are running. |
40892367b tracing: Kconfig ... |
459 |
If unsure, say N. |
5092dbc96 ring-buffer: add ... |
460 |
|
4ed9f0716 tracing: create m... |
461 |
endif # FTRACE |
40ada30f9 tracing: clean up... |
462 463 |
endif # TRACING_SUPPORT |