blob: cd3134510f3d0b9d807a532d6d9ab271e98a40f1 [file] [log] [blame]
Arnaldo Carvalho de Melo16444a82008-05-12 21:20:42 +02001#
Steven Rostedt606576c2008-10-06 19:06:12 -04002# Architectures that offer an FUNCTION_TRACER implementation should
3# select HAVE_FUNCTION_TRACER:
Arnaldo Carvalho de Melo16444a82008-05-12 21:20:42 +02004#
Frédéric Weisbecker2a3a4f62008-09-21 20:12:14 +02005
Török Edwin8d264872008-11-23 12:39:08 +02006config USER_STACKTRACE_SUPPORT
7 bool
8
Frédéric Weisbecker2a3a4f62008-09-21 20:12:14 +02009config NOP_TRACER
10 bool
11
Steven Rostedt78d904b2009-02-05 18:43:07 -050012config HAVE_FTRACE_NMI_ENTER
13 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040014 help
Randy Dunlap40892362009-12-21 12:01:17 -080015 See Documentation/trace/ftrace-design.txt
Steven Rostedt78d904b2009-02-05 18:43:07 -050016
Steven Rostedt606576c2008-10-06 19:06:12 -040017config HAVE_FUNCTION_TRACER
Arnaldo Carvalho de Melo16444a82008-05-12 21:20:42 +020018 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040019 help
Randy Dunlap40892362009-12-21 12:01:17 -080020 See Documentation/trace/ftrace-design.txt
Steven Rostedtbc0c38d2008-05-12 21:20:42 +020021
Frederic Weisbeckerfb526072008-11-25 21:07:04 +010022config HAVE_FUNCTION_GRAPH_TRACER
Frederic Weisbecker15e6cb32008-11-11 07:14:25 +010023 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040024 help
Randy Dunlap40892362009-12-21 12:01:17 -080025 See Documentation/trace/ftrace-design.txt
Frederic Weisbecker15e6cb32008-11-11 07:14:25 +010026
Steven Rostedt71e308a2009-06-18 12:45:08 -040027config HAVE_FUNCTION_GRAPH_FP_TEST
28 bool
29 help
Mike Frysinger03688972010-01-22 08:12:47 -050030 See Documentation/trace/ftrace-design.txt
Steven Rostedt71e308a2009-06-18 12:45:08 -040031
Steven Rostedt60a7ecf2008-11-05 16:05:44 -050032config HAVE_FUNCTION_TRACE_MCOUNT_TEST
33 bool
34 help
Randy Dunlap40892362009-12-21 12:01:17 -080035 See Documentation/trace/ftrace-design.txt
Steven Rostedt60a7ecf2008-11-05 16:05:44 -050036
Steven Rostedt677aa9f2008-05-17 00:01:36 -040037config HAVE_DYNAMIC_FTRACE
38 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040039 help
Randy Dunlap40892362009-12-21 12:01:17 -080040 See Documentation/trace/ftrace-design.txt
Steven Rostedt677aa9f2008-05-17 00:01:36 -040041
Steven Rostedt8da38212008-08-14 15:45:07 -040042config HAVE_FTRACE_MCOUNT_RECORD
43 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040044 help
Randy Dunlap40892362009-12-21 12:01:17 -080045 See Documentation/trace/ftrace-design.txt
Steven Rostedt8da38212008-08-14 15:45:07 -040046
Josh Stone66700002009-08-24 14:43:11 -070047config HAVE_SYSCALL_TRACEPOINTS
Frederic Weisbeckeree08c6e2009-03-07 05:52:59 +010048 bool
Mike Frysinger555f3862009-09-14 20:10:15 -040049 help
Randy Dunlap40892362009-12-21 12:01:17 -080050 See Documentation/trace/ftrace-design.txt
Frederic Weisbeckeree08c6e2009-03-07 05:52:59 +010051
Steven Rostedtcf4db252010-10-14 23:32:44 -040052config HAVE_C_RECORDMCOUNT
Steven Rostedt72441cb2010-10-13 17:12:30 -040053 bool
54 help
55 C version of recordmcount available?
56
Steven Rostedt352ad252008-05-12 21:20:42 +020057config TRACER_MAX_TRACE
58 bool
59
Steven Rostedt7a8e76a2008-09-29 23:02:38 -040060config RING_BUFFER
61 bool
62
Steven Rostedt78d904b2009-02-05 18:43:07 -050063config FTRACE_NMI_ENTER
64 bool
65 depends on HAVE_FTRACE_NMI_ENTER
66 default y
67
Tom Zanussi5f77a882009-04-08 03:14:01 -050068config EVENT_TRACING
Zhaoleib11c53e2009-05-25 18:11:59 +080069 select CONTEXT_SWITCH_TRACER
70 bool
71
Thomas Renninger25e41932011-01-03 17:50:44 +010072config 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,
Jesper Juhlf6292992011-07-24 23:15:42 +020085 namely 3.1.
Thomas Renninger25e41932011-01-03 17:50:44 +010086
Zhaoleib11c53e2009-05-25 18:11:59 +080087config CONTEXT_SWITCH_TRACER
Tom Zanussi5f77a882009-04-08 03:14:01 -050088 bool
89
Steven Rostedt85bac322009-09-04 14:24:40 -040090config 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
Steven Rostedt5e0a0932009-05-28 15:50:13 -040096# 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
Randy Dunlap40892362009-12-21 12:01:17 -0800101# hiding of the automatic options.
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400102
Steven Rostedtbc0c38d2008-05-12 21:20:42 +0200103config TRACING
104 bool
105 select DEBUG_FS
Steven Rostedt7a8e76a2008-09-29 23:02:38 -0400106 select RING_BUFFER
Al Viroc2c80522008-10-31 19:50:41 +0000107 select STACKTRACE if STACKTRACE_SUPPORT
Ingo Molnar5f87f112008-07-23 14:15:22 +0200108 select TRACEPOINTS
Steven Rostedtf3384b22008-10-29 11:15:57 -0400109 select NOP_TRACER
Frederic Weisbecker769b0442009-03-06 17:21:49 +0100110 select BINARY_PRINTF
Tom Zanussi5f77a882009-04-08 03:14:01 -0500111 select EVENT_TRACING
Steven Rostedtbc0c38d2008-05-12 21:20:42 +0200112
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400113config GENERIC_TRACER
114 bool
115 select TRACING
116
Ingo Molnar40ada302009-03-05 21:19:55 +0100117#
118# Minimum requirements an architecture has to meet for us to
119# be able to offer generic tracing facilities:
120#
121config TRACING_SUPPORT
122 bool
Anton Vorontsov45b95602009-03-24 01:07:24 +0300123 # 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
Ingo Molnar40ada302009-03-05 21:19:55 +0100128 depends on STACKTRACE_SUPPORT
KOSAKI Motohiro422d3c72009-03-06 10:40:53 +0900129 default y
Ingo Molnar40ada302009-03-05 21:19:55 +0100130
131if TRACING_SUPPORT
132
Steven Rostedt4ed9f072009-04-20 10:47:36 -0400133menuconfig FTRACE
134 bool "Tracers"
Steven Rostedt65b77242009-05-07 12:49:27 -0400135 default y if DEBUG_KERNEL
Steven Rostedt4ed9f072009-04-20 10:47:36 -0400136 help
Randy Dunlap40892362009-12-21 12:01:17 -0800137 Enable the kernel tracing infrastructure.
Steven Rostedt4ed9f072009-04-20 10:47:36 -0400138
139if FTRACE
Peter Zijlstra17d80fd2008-10-21 16:31:18 +0200140
Steven Rostedt606576c2008-10-06 19:06:12 -0400141config FUNCTION_TRACER
Steven Rostedt1b29b012008-05-12 21:20:42 +0200142 bool "Kernel Function Tracer"
Steven Rostedt606576c2008-10-06 19:06:12 -0400143 depends on HAVE_FUNCTION_TRACER
Michal Simekd20ac252011-04-04 11:20:12 +0200144 select FRAME_POINTER if !ARM_UNWIND && !S390 && !MICROBLAZE
Steven Rostedt4d7a0772009-02-18 22:06:18 -0500145 select KALLSYMS
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400146 select GENERIC_TRACER
Steven Rostedt35e8e302008-05-12 21:20:42 +0200147 select CONTEXT_SWITCH_TRACER
Steven Rostedt1b29b012008-05-12 21:20:42 +0200148 help
149 Enable the kernel to trace every kernel function. This is done
150 by using a compiler feature to insert a small, 5-byte No-Operation
Randy Dunlap40892362009-12-21 12:01:17 -0800151 instruction at the beginning of every kernel function, which NOP
Steven Rostedt1b29b012008-05-12 21:20:42 +0200152 sequence is then dynamically patched into a tracer call when
153 tracing is enabled by the administrator. If it's runtime disabled
154 (the bootup default), then the overhead of the instructions is very
155 small and not measurable even in micro-benchmarks.
Steven Rostedt35e8e302008-05-12 21:20:42 +0200156
Frederic Weisbeckerfb526072008-11-25 21:07:04 +0100157config FUNCTION_GRAPH_TRACER
158 bool "Kernel Function Graph Tracer"
159 depends on HAVE_FUNCTION_GRAPH_TRACER
Frederic Weisbecker15e6cb32008-11-11 07:14:25 +0100160 depends on FUNCTION_TRACER
Steven Rostedteb4a0372009-06-18 12:53:21 -0400161 depends on !X86_32 || !CC_OPTIMIZE_FOR_SIZE
Ingo Molnar764f3b92008-12-03 10:33:58 +0100162 default y
Frederic Weisbecker15e6cb32008-11-11 07:14:25 +0100163 help
Frederic Weisbeckerfb526072008-11-25 21:07:04 +0100164 Enable the kernel to trace a function at both its return
165 and its entry.
Matt LaPlante692105b2009-01-26 11:12:25 +0100166 Its first purpose is to trace the duration of functions and
167 draw a call graph for each thread with some information like
Randy Dunlap40892362009-12-21 12:01:17 -0800168 the return value. This is done by setting the current return
Matt LaPlante692105b2009-01-26 11:12:25 +0100169 address on the current task structure into a stack of calls.
Frederic Weisbecker15e6cb32008-11-11 07:14:25 +0100170
Steven Rostedtbac429f2009-03-20 12:50:56 -0400171
Steven Rostedt81d68a92008-05-12 21:20:42 +0200172config IRQSOFF_TRACER
173 bool "Interrupts-off Latency Tracer"
174 default n
175 depends on TRACE_IRQFLAGS_SUPPORT
John Stultz592913e2010-07-13 17:56:20 -0700176 depends on !ARCH_USES_GETTIMEOFFSET
Steven Rostedt81d68a92008-05-12 21:20:42 +0200177 select TRACE_IRQFLAGS
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400178 select GENERIC_TRACER
Steven Rostedt81d68a92008-05-12 21:20:42 +0200179 select TRACER_MAX_TRACE
Steven Rostedt85bac322009-09-04 14:24:40 -0400180 select RING_BUFFER_ALLOW_SWAP
Steven Rostedt81d68a92008-05-12 21:20:42 +0200181 help
182 This option measures the time spent in irqs-off critical
183 sections, with microsecond accuracy.
184
185 The default measurement method is a maximum search, which is
186 disabled by default and can be runtime (re-)started
187 via:
188
GeunSik Lim156f5a72009-06-02 15:01:37 +0900189 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
Steven Rostedt81d68a92008-05-12 21:20:42 +0200190
Randy Dunlap40892362009-12-21 12:01:17 -0800191 (Note that kernel size and overhead increase with this option
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200192 enabled. This option and the preempt-off timing option can be
193 used together or separately.)
194
195config PREEMPT_TRACER
196 bool "Preemption-off Latency Tracer"
197 default n
John Stultz592913e2010-07-13 17:56:20 -0700198 depends on !ARCH_USES_GETTIMEOFFSET
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200199 depends on PREEMPT
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400200 select GENERIC_TRACER
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200201 select TRACER_MAX_TRACE
Steven Rostedt85bac322009-09-04 14:24:40 -0400202 select RING_BUFFER_ALLOW_SWAP
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200203 help
Randy Dunlap40892362009-12-21 12:01:17 -0800204 This option measures the time spent in preemption-off critical
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200205 sections, with microsecond accuracy.
206
207 The default measurement method is a maximum search, which is
208 disabled by default and can be runtime (re-)started
209 via:
210
GeunSik Lim156f5a72009-06-02 15:01:37 +0900211 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200212
Randy Dunlap40892362009-12-21 12:01:17 -0800213 (Note that kernel size and overhead increase with this option
Steven Rostedt6cd8a4b2008-05-12 21:20:42 +0200214 enabled. This option and the irqs-off timing option can be
215 used together or separately.)
216
Steven Rostedt352ad252008-05-12 21:20:42 +0200217config SCHED_TRACER
218 bool "Scheduling Latency Tracer"
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400219 select GENERIC_TRACER
Steven Rostedt352ad252008-05-12 21:20:42 +0200220 select CONTEXT_SWITCH_TRACER
221 select TRACER_MAX_TRACE
222 help
223 This tracer tracks the latency of the highest priority task
224 to be scheduled in, starting from the point it has woken up.
225
Steven Rostedt897f17a2009-05-28 16:31:21 -0400226config ENABLE_DEFAULT_TRACERS
227 bool "Trace process context switches and events"
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400228 depends on !GENERIC_TRACER
Steven Rostedtb77e38a2009-02-24 10:21:36 -0500229 select TRACING
230 help
Randy Dunlap40892362009-12-21 12:01:17 -0800231 This tracer hooks to various trace points in the kernel,
Steven Rostedtb77e38a2009-02-24 10:21:36 -0500232 allowing the user to pick and choose which trace point they
Steven Rostedt897f17a2009-05-28 16:31:21 -0400233 want to trace. It also includes the sched_switch tracer plugin.
Steven Rostedta7abe972009-04-20 10:59:34 -0400234
Frederic Weisbeckeree08c6e2009-03-07 05:52:59 +0100235config FTRACE_SYSCALLS
236 bool "Trace syscalls"
Josh Stone66700002009-08-24 14:43:11 -0700237 depends on HAVE_SYSCALL_TRACEPOINTS
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400238 select GENERIC_TRACER
Frederic Weisbecker0ea1c412009-03-15 22:10:38 +0100239 select KALLSYMS
Frederic Weisbeckeree08c6e2009-03-07 05:52:59 +0100240 help
241 Basic tracer to catch the syscall entry and exit events.
242
Steven Rostedt2ed84ee2008-11-12 15:24:24 -0500243config TRACE_BRANCH_PROFILING
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400244 bool
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400245 select GENERIC_TRACER
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400246
247choice
248 prompt "Branch Profiling"
249 default BRANCH_PROFILE_NONE
250 help
251 The branch profiling is a software profiler. It will add hooks
252 into the C conditionals to test which path a branch takes.
253
254 The likely/unlikely profiler only looks at the conditions that
255 are annotated with a likely or unlikely macro.
256
Randy Dunlap40892362009-12-21 12:01:17 -0800257 The "all branch" profiler will profile every if-statement in the
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400258 kernel. This profiler will also enable the likely/unlikely
Randy Dunlap40892362009-12-21 12:01:17 -0800259 profiler.
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400260
Randy Dunlap40892362009-12-21 12:01:17 -0800261 Either of the above profilers adds a bit of overhead to the system.
262 If unsure, choose "No branch profiling".
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400263
264config BRANCH_PROFILE_NONE
265 bool "No branch profiling"
266 help
Randy Dunlap40892362009-12-21 12:01:17 -0800267 No branch profiling. Branch profiling adds a bit of overhead.
268 Only enable it if you want to analyse the branching behavior.
269 Otherwise keep it disabled.
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400270
271config PROFILE_ANNOTATED_BRANCHES
272 bool "Trace likely/unlikely profiler"
273 select TRACE_BRANCH_PROFILING
Steven Rostedt1f0d69a2008-11-12 00:14:39 -0500274 help
275 This tracer profiles all the the likely and unlikely macros
276 in the kernel. It will display the results in:
277
David Rientjes13e5bef2011-03-16 17:17:08 -0700278 /sys/kernel/debug/tracing/trace_stat/branch_annotated
Steven Rostedt1f0d69a2008-11-12 00:14:39 -0500279
Randy Dunlap40892362009-12-21 12:01:17 -0800280 Note: this will add a significant overhead; only turn this
Steven Rostedt1f0d69a2008-11-12 00:14:39 -0500281 on if you need to profile the system's use of these macros.
282
Steven Rostedt2bcd5212008-11-21 01:30:54 -0500283config PROFILE_ALL_BRANCHES
284 bool "Profile all if conditionals"
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400285 select TRACE_BRANCH_PROFILING
Steven Rostedt2bcd5212008-11-21 01:30:54 -0500286 help
287 This tracer profiles all branch conditions. Every if ()
288 taken in the kernel is recorded whether it hit or miss.
289 The results will be displayed in:
290
David Rientjes13e5bef2011-03-16 17:17:08 -0700291 /sys/kernel/debug/tracing/trace_stat/branch_all
Steven Rostedt2bcd5212008-11-21 01:30:54 -0500292
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400293 This option also enables the likely/unlikely profiler.
294
Steven Rostedt2bcd5212008-11-21 01:30:54 -0500295 This configuration, when enabled, will impose a great overhead
296 on the system. This should only be enabled when the system
Randy Dunlap40892362009-12-21 12:01:17 -0800297 is to be analyzed in much detail.
Steven Rostedt9ae5b872009-04-20 10:27:58 -0400298endchoice
Steven Rostedt2bcd5212008-11-21 01:30:54 -0500299
Steven Rostedt2ed84ee2008-11-12 15:24:24 -0500300config TRACING_BRANCHES
Steven Rostedt52f232c2008-11-12 00:14:40 -0500301 bool
302 help
303 Selected by tracers that will trace the likely and unlikely
304 conditions. This prevents the tracers themselves from being
305 profiled. Profiling the tracing infrastructure can only happen
306 when the likelys and unlikelys are not being traced.
307
Steven Rostedt2ed84ee2008-11-12 15:24:24 -0500308config BRANCH_TRACER
Steven Rostedt52f232c2008-11-12 00:14:40 -0500309 bool "Trace likely/unlikely instances"
Steven Rostedt2ed84ee2008-11-12 15:24:24 -0500310 depends on TRACE_BRANCH_PROFILING
311 select TRACING_BRANCHES
Steven Rostedt52f232c2008-11-12 00:14:40 -0500312 help
313 This traces the events of likely and unlikely condition
314 calls in the kernel. The difference between this and the
315 "Trace likely/unlikely profiler" is that this is not a
316 histogram of the callers, but actually places the calling
317 events into a running trace buffer to see when and where the
318 events happened, as well as their results.
319
320 Say N if unsure.
321
Steven Rostedte5a81b62008-08-27 23:31:01 -0400322config STACK_TRACER
323 bool "Trace max stack"
Steven Rostedt606576c2008-10-06 19:06:12 -0400324 depends on HAVE_FUNCTION_TRACER
Steven Rostedt606576c2008-10-06 19:06:12 -0400325 select FUNCTION_TRACER
Steven Rostedte5a81b62008-08-27 23:31:01 -0400326 select STACKTRACE
Steven Rostedt4d7a0772009-02-18 22:06:18 -0500327 select KALLSYMS
Steven Rostedte5a81b62008-08-27 23:31:01 -0400328 help
Ingo Molnar4519d9e2008-10-14 14:15:43 +0200329 This special tracer records the maximum stack footprint of the
GeunSik Lim156f5a72009-06-02 15:01:37 +0900330 kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
Ingo Molnar4519d9e2008-10-14 14:15:43 +0200331
332 This tracer works by hooking into every function call that the
333 kernel executes, and keeping a maximum stack depth value and
Steven Rostedtf38f1d22008-12-16 23:06:40 -0500334 stack-trace saved. If this is configured with DYNAMIC_FTRACE
335 then it will not have any overhead while the stack tracer
336 is disabled.
337
338 To enable the stack tracer on bootup, pass in 'stacktrace'
339 on the kernel command line.
340
341 The stack tracer can also be enabled or disabled via the
342 sysctl kernel.stack_tracer_enabled
Ingo Molnar4519d9e2008-10-14 14:15:43 +0200343
344 Say N if unsure.
Steven Rostedte5a81b62008-08-27 23:31:01 -0400345
Frederic Weisbecker2db270a2009-02-07 20:46:45 +0100346config BLK_DEV_IO_TRACE
Randy Dunlap40892362009-12-21 12:01:17 -0800347 bool "Support for tracing block IO actions"
Frederic Weisbecker2db270a2009-02-07 20:46:45 +0100348 depends on SYSFS
Ingo Molnar1dfba052009-02-09 12:06:54 +0100349 depends on BLOCK
Frederic Weisbecker2db270a2009-02-07 20:46:45 +0100350 select RELAY
351 select DEBUG_FS
352 select TRACEPOINTS
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400353 select GENERIC_TRACER
Frederic Weisbecker2db270a2009-02-07 20:46:45 +0100354 select STACKTRACE
355 help
356 Say Y here if you want to be able to trace the block layer actions
357 on a given queue. Tracing allows you to see any traffic happening
358 on a block device queue. For more information (and the userspace
359 support tools needed), fetch the blktrace tools from:
360
361 git://git.kernel.dk/blktrace.git
362
363 Tracing also is possible using the ftrace interface, e.g.:
364
365 echo 1 > /sys/block/sda/sda1/trace/enable
366 echo blk > /sys/kernel/debug/tracing/current_tracer
367 cat /sys/kernel/debug/tracing/trace_pipe
368
369 If unsure, say N.
Frederic Weisbecker36994e52008-12-29 13:42:23 -0800370
Masami Hiramatsu77b44d12009-11-03 19:12:47 -0500371config KPROBE_EVENT
Masami Hiramatsu413d37d2009-08-13 16:35:11 -0400372 depends on KPROBES
Heiko Carstensf850c302010-02-10 17:25:17 +0100373 depends on HAVE_REGS_AND_STACK_ACCESS_API
Masami Hiramatsu77b44d12009-11-03 19:12:47 -0500374 bool "Enable kprobes-based dynamic events"
Masami Hiramatsu413d37d2009-08-13 16:35:11 -0400375 select TRACING
Masami Hiramatsu77b44d12009-11-03 19:12:47 -0500376 default y
Masami Hiramatsu413d37d2009-08-13 16:35:11 -0400377 help
Randy Dunlap40892362009-12-21 12:01:17 -0800378 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.
Masami Hiramatsu77b44d12009-11-03 19:12:47 -0500381
382 Those events can be inserted wherever kprobes can probe, and record
383 various register and memory values.
384
Randy Dunlap40892362009-12-21 12:01:17 -0800385 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.
Masami Hiramatsu413d37d2009-08-13 16:35:11 -0400387
Steven Rostedt3d083392008-05-12 21:20:42 +0200388config DYNAMIC_FTRACE
389 bool "enable/disable ftrace tracepoints dynamically"
Steven Rostedt606576c2008-10-06 19:06:12 -0400390 depends on FUNCTION_TRACER
Steven Rostedt677aa9f2008-05-17 00:01:36 -0400391 depends on HAVE_DYNAMIC_FTRACE
Steven Rostedt3d083392008-05-12 21:20:42 +0200392 default y
393 help
Randy Dunlap40892362009-12-21 12:01:17 -0800394 This option will modify all the calls to ftrace dynamically
395 (will patch them out of the binary image and replace them
396 with a No-Op instruction) as they are called. A table is
397 created to dynamically enable them again.
Steven Rostedt3d083392008-05-12 21:20:42 +0200398
Randy Dunlap40892362009-12-21 12:01:17 -0800399 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but
400 otherwise has native performance as long as no tracing is active.
Steven Rostedt3d083392008-05-12 21:20:42 +0200401
Randy Dunlap40892362009-12-21 12:01:17 -0800402 The changes to the code are done by a kernel thread that
403 wakes up once a second and checks to see if any ftrace calls
404 were made. If so, it runs stop_machine (stops all CPUS)
405 and modifies the code to jump over the call to ftrace.
Steven Rostedt60a11772008-05-12 21:20:44 +0200406
Steven Rostedtbac429f2009-03-20 12:50:56 -0400407config FUNCTION_PROFILER
408 bool "Kernel function profiler"
Steven Rostedt493762f2009-03-23 17:12:36 -0400409 depends on FUNCTION_TRACER
Steven Rostedtbac429f2009-03-20 12:50:56 -0400410 default n
411 help
Randy Dunlap40892362009-12-21 12:01:17 -0800412 This option enables the kernel function profiler. A file is created
413 in debugfs called function_profile_enabled which defaults to zero.
414 When a 1 is echoed into this file profiling begins, and when a
415 zero is entered, profiling stops. A "functions" file is created in
416 the trace_stats directory; this file shows the list of functions that
417 have been hit and their counters.
Steven Rostedtbac429f2009-03-20 12:50:56 -0400418
Randy Dunlap40892362009-12-21 12:01:17 -0800419 If in doubt, say N.
Steven Rostedtbac429f2009-03-20 12:50:56 -0400420
Steven Rostedt8da38212008-08-14 15:45:07 -0400421config FTRACE_MCOUNT_RECORD
422 def_bool y
423 depends on DYNAMIC_FTRACE
424 depends on HAVE_FTRACE_MCOUNT_RECORD
425
Steven Rostedt60a11772008-05-12 21:20:44 +0200426config FTRACE_SELFTEST
427 bool
428
429config FTRACE_STARTUP_TEST
430 bool "Perform a startup test on ftrace"
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400431 depends on GENERIC_TRACER
Steven Rostedt60a11772008-05-12 21:20:44 +0200432 select FTRACE_SELFTEST
433 help
434 This option performs a series of startup tests on ftrace. On bootup
435 a series of tests are made to verify that the tracer is
436 functioning properly. It will do tests on all the configured
437 tracers of ftrace.
Peter Zijlstra17d80fd2008-10-21 16:31:18 +0200438
Steven Rostedt1f5a6b42009-09-14 11:58:24 -0400439config EVENT_TRACE_TEST_SYSCALLS
440 bool "Run selftest on syscall events"
441 depends on FTRACE_STARTUP_TEST
442 help
443 This option will also enable testing every syscall event.
444 It only enables the event and disables it and runs various loads
445 with the event enabled. This adds a bit more time for kernel boot
446 up since it runs this on every system call defined.
447
448 TBD - enable a way to actually call the syscalls as we test their
449 events
450
Pekka Paalanenfe6f90e2009-01-03 21:23:51 +0200451config MMIOTRACE
452 bool "Memory mapped IO tracing"
Ingo Molnar40ada302009-03-05 21:19:55 +0100453 depends on HAVE_MMIOTRACE_SUPPORT && PCI
Steven Rostedt5e0a0932009-05-28 15:50:13 -0400454 select GENERIC_TRACER
Pekka Paalanenfe6f90e2009-01-03 21:23:51 +0200455 help
456 Mmiotrace traces Memory Mapped I/O access and is meant for
457 debugging and reverse engineering. It is called from the ioremap
458 implementation and works via page faults. Tracing is disabled by
459 default and can be enabled at run-time.
460
Li Zefan4d1f4372009-04-10 08:48:36 +0800461 See Documentation/trace/mmiotrace.txt.
Pekka Paalanenfe6f90e2009-01-03 21:23:51 +0200462 If you are not helping to develop drivers, say N.
463
464config MMIOTRACE_TEST
465 tristate "Test module for mmiotrace"
466 depends on MMIOTRACE && m
467 help
468 This is a dumb module for testing mmiotrace. It is very dangerous
469 as it will write garbage to IO memory starting at a given address.
470 However, it should be safe to use on e.g. unused portion of VRAM.
471
472 Say N, unless you absolutely know what you are doing.
473
Steven Rostedt5092dbc2009-05-05 22:47:18 -0400474config RING_BUFFER_BENCHMARK
475 tristate "Ring buffer benchmark stress tester"
476 depends on RING_BUFFER
477 help
Randy Dunlap40892362009-12-21 12:01:17 -0800478 This option creates a test to stress the ring buffer and benchmark it.
479 It creates its own ring buffer such that it will not interfere with
Steven Rostedt5092dbc2009-05-05 22:47:18 -0400480 any other users of the ring buffer (such as ftrace). It then creates
481 a producer and consumer that will run for 10 seconds and sleep for
482 10 seconds. Each interval it will print out the number of events
483 it recorded and give a rough estimate of how long each iteration took.
484
485 It does not disable interrupts or raise its priority, so it may be
486 affected by processes that are running.
487
Randy Dunlap40892362009-12-21 12:01:17 -0800488 If unsure, say N.
Steven Rostedt5092dbc2009-05-05 22:47:18 -0400489
Steven Rostedt4ed9f072009-04-20 10:47:36 -0400490endif # FTRACE
Ingo Molnar40ada302009-03-05 21:19:55 +0100491
492endif # TRACING_SUPPORT
493