blob: 748e72be6e68364225846cadf5dd6d6a6990e9a8 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001
2config PRINTK_TIME
3 bool "Show timing information on printks"
Randy Dunlapd3b8b6e2006-12-06 20:36:38 -08004 depends on PRINTK
Linus Torvalds1da177e2005-04-16 15:20:36 -07005 help
6 Selecting this option causes timing information to be
7 included in printk output. This allows you to measure
8 the interval between kernel operations, including bootup
9 operations. This is useful for identifying long delays
10 in kernel startup.
11
Jeff Garzikde488442007-10-25 04:06:13 -040012config ENABLE_WARN_DEPRECATED
13 bool "Enable __deprecated logic"
14 default y
15 help
16 Enable the __deprecated logic in the kernel build.
17 Disable this to suppress the "warning: 'foo' is deprecated
18 (declared at kernel/power/somefile.c:1234)" messages.
19
Andrew Mortoncebc04b2006-08-14 22:43:18 -070020config ENABLE_MUST_CHECK
21 bool "Enable __must_check logic"
22 default y
23 help
24 Enable the __must_check logic in the kernel build. Disable this to
25 suppress the "warning: ignoring return value of 'foo', declared with
26 attribute warn_unused_result" messages.
Linus Torvalds1da177e2005-04-16 15:20:36 -070027
Linus Torvalds1da177e2005-04-16 15:20:36 -070028config MAGIC_SYSRQ
29 bool "Magic SysRq key"
Adrian Bunkf346f4b2006-01-09 20:54:51 -080030 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -070031 help
32 If you say Y here, you will have some control over the system even
33 if the system crashes for example during kernel debugging (e.g., you
34 will be able to flush the buffer cache to disk, reboot the system
35 immediately or dump some status information). This is accomplished
36 by pressing various keys while holding SysRq (Alt+PrintScreen). It
37 also works on a serial console (on PC hardware at least), if you
38 send a BREAK and then within 5 seconds a command keypress. The
39 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
40 unless you really know what this hack does.
41
Arjan van de Venf71d20e2006-06-28 04:26:45 -070042config UNUSED_SYMBOLS
43 bool "Enable unused/obsolete exported symbols"
44 default y if X86
45 help
46 Unused but exported symbols make the kernel needlessly bigger. For
47 that reason most of these unused exports will soon be removed. This
48 option is provided temporarily to provide a transition period in case
49 some external kernel module needs one of these symbols anyway. If you
50 encounter such a case in your module, consider if you are actually
51 using the right API. (rationale: since nobody in the kernel is using
52 this in a module, there is a pretty good chance it's actually the
53 wrong interface to use). If you really need the symbol, please send a
54 mail to the linux kernel mailing list mentioning the symbol and why
55 you really need it, and what the merge plan to the mainline kernel for
56 your module is.
57
Don Mullisbf4735a2006-12-10 02:18:37 -080058config DEBUG_FS
59 bool "Debug Filesystem"
60 depends on SYSFS
61 help
62 debugfs is a virtual file system that kernel developers use to put
63 debugging files into. Enable this option to be able to read and
64 write to these files.
65
66 If unsure, say N.
67
68config HEADERS_CHECK
69 bool "Run 'make headers_check' when building vmlinux"
70 depends on !UML
71 help
72 This option will extract the user-visible kernel headers whenever
73 building the kernel, and will run basic sanity checks on them to
74 ensure that exported files do not attempt to include files which
75 were not exported, etc.
76
77 If you're making modifications to header files which are
78 relevant for userspace, say 'Y', and check the headers
79 exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
80 your build tree), to make sure they're suitable.
81
Sam Ravnborg91341d42008-01-21 21:31:44 +010082config DEBUG_SECTION_MISMATCH
83 bool "Enable full Section mismatch analysis"
84 default n
85 help
86 The section mismatch analysis checks if there are illegal
87 references from one section to another section.
88 Linux will during link or during runtime drop some sections
89 and any use of code/data previously in these sections will
90 most likely result in an oops.
91 In the code functions and variables are annotated with
92 __init, __devinit etc. (see full list in include/linux/init.h)
93 which result in the code/data being placed in specific sections.
94 The section mismatch anaylsis are always done after a full
95 kernel build but enabling this options will in addition
96 do the following:
97 - Add the option -fno-inline-functions-called-once to gcc
98 When inlining a function annotated __init in a non-init
99 function we would loose the section information and thus
100 the analysis would not catch the illegal reference.
101 This options tell gcc to inline less but will also
102 result in a larger kernel.
103 - Run the section mismatch analysis for each module/built-in.o
104 When we run the section mismatch analysis on vmlinux.o we
105 looses valueable information about where the mismatch was
106 introduced.
107 Running the analysis for each module/built-in.o file
108 will tell where the mismatch happens much closer to the
109 source. The drawback is that we will report the same
110 mismatch at least twice.
111
Adrian Bunkf346f4b2006-01-09 20:54:51 -0800112config DEBUG_KERNEL
113 bool "Kernel debugging"
114 help
115 Say Y here if you are developing drivers or trying to debug and
116 identify kernel problems.
117
David Woodhousea304e1b2007-02-12 00:52:00 -0800118config DEBUG_SHIRQ
119 bool "Debug shared IRQ handlers"
120 depends on DEBUG_KERNEL && GENERIC_HARDIRQS
121 help
122 Enable this to generate a spurious interrupt as soon as a shared
123 interrupt handler is registered, and just before one is deregistered.
124 Drivers ought to be able to handle interrupts coming in at those
125 points; some don't and need to be caught.
126
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700127config DETECT_SOFTLOCKUP
128 bool "Detect Soft Lockups"
Heiko Carstensdea20a32006-10-11 01:20:44 -0700129 depends on DEBUG_KERNEL && !S390
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700130 default y
131 help
132 Say Y here to enable the kernel to detect "soft lockups",
133 which are bugs that cause the kernel to loop in kernel
134 mode for more than 10 seconds, without giving other tasks a
135 chance to run.
136
137 When a soft-lockup is detected, the kernel will print the
138 current stack trace (which you should report), but the
139 system will stay locked up. This feature has negligible
140 overhead.
141
142 (Note that "hard lockups" are separate type of bugs that
143 can be detected via the NMI-watchdog, on platforms that
144 support it.)
145
Ingo Molnarb642b6d2007-07-09 18:52:00 +0200146config SCHED_DEBUG
147 bool "Collect scheduler debugging info"
148 depends on DEBUG_KERNEL && PROC_FS
149 default y
150 help
151 If you say Y here, the /proc/sched_debug file will be provided
152 that can help debug the scheduler. The runtime overhead of this
153 option is minimal.
154
Linus Torvalds1da177e2005-04-16 15:20:36 -0700155config SCHEDSTATS
156 bool "Collect scheduler statistics"
157 depends on DEBUG_KERNEL && PROC_FS
158 help
159 If you say Y here, additional code will be inserted into the
160 scheduler and related routines to collect statistics about
161 scheduler behavior and provide them in /proc/schedstat. These
162 stats may be useful for both tuning and debugging the scheduler
163 If you aren't debugging the scheduler or trying to tune a specific
164 application, you can say N to avoid the very slight overhead
165 this adds.
166
Ingo Molnar82f67cd2007-02-16 01:28:13 -0800167config TIMER_STATS
168 bool "Collect kernel timers statistics"
169 depends on DEBUG_KERNEL && PROC_FS
170 help
171 If you say Y here, additional code will be inserted into the
172 timer routines to collect statistics about kernel timers being
173 reprogrammed. The statistics can be read from /proc/timer_stats.
174 The statistics collection is started by writing 1 to /proc/timer_stats,
175 writing 0 stops it. This feature is useful to collect information
Ingo Molnarc1a834d2007-06-01 00:47:16 -0700176 about timer usage patterns in kernel and userspace. This feature
177 is lightweight if enabled in the kernel config but not activated
178 (it defaults to deactivated on bootup and will only be activated
179 if some application like powertop activates it explicitly).
Ingo Molnar82f67cd2007-02-16 01:28:13 -0800180
Linus Torvalds1da177e2005-04-16 15:20:36 -0700181config DEBUG_SLAB
Andrew Morton4a2f0ac2006-03-25 03:07:22 -0800182 bool "Debug slab memory allocations"
Ingo Molnar50dd26b2006-01-08 01:01:42 -0800183 depends on DEBUG_KERNEL && SLAB
Linus Torvalds1da177e2005-04-16 15:20:36 -0700184 help
185 Say Y here to have the kernel do limited verification on memory
186 allocation as well as poisoning memory on free to catch use of freed
187 memory. This can make kmalloc/kfree-intensive workloads much slower.
188
Al Viro871751e2006-03-25 03:06:39 -0800189config DEBUG_SLAB_LEAK
190 bool "Memory leak debugging"
191 depends on DEBUG_SLAB
192
Christoph Lameterf0630ff2007-07-15 23:38:14 -0700193config SLUB_DEBUG_ON
194 bool "SLUB debugging on by default"
195 depends on SLUB && SLUB_DEBUG
196 default n
197 help
198 Boot with debugging on by default. SLUB boots by default with
199 the runtime debug capabilities switched off. Enabling this is
200 equivalent to specifying the "slub_debug" parameter on boot.
201 There is no support for more fine grained debug control like
202 possible with slub_debug=xxx. SLUB debugging may be switched
203 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
204 "slub_debug=-".
205
Linus Torvalds1da177e2005-04-16 15:20:36 -0700206config DEBUG_PREEMPT
207 bool "Debug preemptible kernel"
Hugh Dickins048c8bc2006-11-01 05:44:54 +1100208 depends on DEBUG_KERNEL && PREEMPT && (TRACE_IRQFLAGS_SUPPORT || PPC64)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700209 default y
210 help
211 If you say Y here then the kernel will use a debug variant of the
212 commonly used smp_processor_id() function and will print warnings
213 if kernel code uses it in a preemption-unsafe way. Also, the kernel
214 will detect preemption count underflows.
215
Ingo Molnare7eebaf2006-06-27 02:54:55 -0700216config DEBUG_RT_MUTEXES
217 bool "RT Mutex debugging, deadlock detection"
Ingo Molnare7eebaf2006-06-27 02:54:55 -0700218 depends on DEBUG_KERNEL && RT_MUTEXES
219 help
220 This allows rt mutex semantics violations and rt mutex related
221 deadlocks (lockups) to be detected and reported automatically.
222
223config DEBUG_PI_LIST
224 bool
225 default y
226 depends on DEBUG_RT_MUTEXES
227
Thomas Gleixner61a87122006-06-27 02:54:56 -0700228config RT_MUTEX_TESTER
229 bool "Built-in scriptable tester for rt-mutexes"
Roman Zippela1583d32006-06-27 02:55:00 -0700230 depends on DEBUG_KERNEL && RT_MUTEXES
Thomas Gleixner61a87122006-06-27 02:54:56 -0700231 help
232 This option enables a rt-mutex tester.
233
Linus Torvalds1da177e2005-04-16 15:20:36 -0700234config DEBUG_SPINLOCK
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700235 bool "Spinlock and rw-lock debugging: basic checks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700236 depends on DEBUG_KERNEL
237 help
238 Say Y here and build SMP to catch missing spinlock initialization
239 and certain other kinds of spinlock errors commonly made. This is
240 best used in conjunction with the NMI watchdog so that spinlock
241 deadlocks are also debuggable.
242
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700243config DEBUG_MUTEXES
244 bool "Mutex debugging: basic checks"
245 depends on DEBUG_KERNEL
246 help
247 This feature allows mutex semantics violations to be detected and
248 reported.
249
Robert P. J. Dayc761c842007-05-08 00:25:02 -0700250config DEBUG_SEMAPHORE
251 bool "Semaphore debugging"
252 depends on DEBUG_KERNEL
253 depends on ALPHA || FRV
254 default n
255 help
256 If you say Y here then semaphore processing will issue lots of
257 verbose debugging messages. If you suspect a semaphore problem or a
258 kernel hacker asks for this option then say Y. Otherwise say N.
259
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700260config DEBUG_LOCK_ALLOC
261 bool "Lock debugging: detect incorrect freeing of live locks"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700262 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700263 select DEBUG_SPINLOCK
264 select DEBUG_MUTEXES
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700265 select LOCKDEP
266 help
267 This feature will check whether any held lock (spinlock, rwlock,
268 mutex or rwsem) is incorrectly freed by the kernel, via any of the
269 memory-freeing routines (kfree(), kmem_cache_free(), free_pages(),
270 vfree(), etc.), whether a live lock is incorrectly reinitialized via
271 spin_lock_init()/mutex_init()/etc., or whether there is any lock
272 held during task exit.
273
274config PROVE_LOCKING
275 bool "Lock debugging: prove locking correctness"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700276 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700277 select LOCKDEP
278 select DEBUG_SPINLOCK
279 select DEBUG_MUTEXES
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700280 select DEBUG_LOCK_ALLOC
281 default n
282 help
283 This feature enables the kernel to prove that all locking
284 that occurs in the kernel runtime is mathematically
285 correct: that under no circumstance could an arbitrary (and
286 not yet triggered) combination of observed locking
287 sequences (on an arbitrary number of CPUs, running an
288 arbitrary number of tasks and interrupt contexts) cause a
289 deadlock.
290
291 In short, this feature enables the kernel to report locking
292 related deadlocks before they actually occur.
293
294 The proof does not depend on how hard and complex a
295 deadlock scenario would be to trigger: how many
296 participant CPUs, tasks and irq-contexts would be needed
297 for it to trigger. The proof also does not depend on
298 timing: if a race and a resulting deadlock is possible
299 theoretically (no matter how unlikely the race scenario
300 is), it will be proven so and will immediately be
301 reported by the kernel (once the event is observed that
302 makes the deadlock theoretically possible).
303
304 If a deadlock is impossible (i.e. the locking rules, as
305 observed by the kernel, are mathematically correct), the
306 kernel reports nothing.
307
308 NOTE: this feature can also be enabled for rwlocks, mutexes
309 and rwsems - in which case all dependencies between these
310 different locking variants are observed and mapped too, and
311 the proof of observed correctness is also maintained for an
312 arbitrary combination of these separate locking variants.
313
314 For more details, see Documentation/lockdep-design.txt.
315
316config LOCKDEP
317 bool
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700318 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700319 select STACKTRACE
Franck Bui-Huu14cf2322007-04-26 00:20:15 -0700320 select FRAME_POINTER if !X86 && !MIPS
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700321 select KALLSYMS
322 select KALLSYMS_ALL
323
Peter Zijlstraf20786f2007-07-19 01:48:56 -0700324config LOCK_STAT
Danny ter Haarfdfb8702007-09-24 21:24:43 -0700325 bool "Lock usage statistics"
Peter Zijlstraf20786f2007-07-19 01:48:56 -0700326 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
327 select LOCKDEP
328 select DEBUG_SPINLOCK
329 select DEBUG_MUTEXES
330 select DEBUG_LOCK_ALLOC
331 default n
332 help
333 This feature enables tracking lock contention points
334
Peter Zijlstraa560aa42007-10-07 00:24:33 -0700335 For more details, see Documentation/lockstat.txt
336
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700337config DEBUG_LOCKDEP
338 bool "Lock dependency engine debugging"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700339 depends on DEBUG_KERNEL && LOCKDEP
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700340 help
341 If you say Y here, the lock dependency engine will do
342 additional runtime checks to debug itself, at the price
343 of more runtime overhead.
344
345config TRACE_IRQFLAGS
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700346 depends on DEBUG_KERNEL
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700347 bool
348 default y
349 depends on TRACE_IRQFLAGS_SUPPORT
350 depends on PROVE_LOCKING
351
Linus Torvalds1da177e2005-04-16 15:20:36 -0700352config DEBUG_SPINLOCK_SLEEP
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700353 bool "Spinlock debugging: sleep-inside-spinlock checking"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354 depends on DEBUG_KERNEL
355 help
356 If you say Y here, various routines which may sleep will become very
357 noisy if they are called with a spinlock held.
358
Ingo Molnarcae2ed92006-07-03 00:24:48 -0700359config DEBUG_LOCKING_API_SELFTESTS
360 bool "Locking API boot-time self-tests"
361 depends on DEBUG_KERNEL
362 help
363 Say Y here if you want the kernel to run a short self-test during
364 bootup. The self-test checks whether common types of locking bugs
365 are detected by debugging mechanisms or not. (if you disable
366 lock debugging then those bugs wont be detected of course.)
367 The following locking APIs are covered: spinlocks, rwlocks,
368 mutexes and rwsems.
369
Ingo Molnar8637c092006-07-03 00:24:38 -0700370config STACKTRACE
371 bool
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700372 depends on DEBUG_KERNEL
Ingo Molnar8637c092006-07-03 00:24:38 -0700373 depends on STACKTRACE_SUPPORT
374
Linus Torvalds1da177e2005-04-16 15:20:36 -0700375config DEBUG_KOBJECT
376 bool "kobject debugging"
377 depends on DEBUG_KERNEL
378 help
379 If you say Y here, some extra kobject debugging messages will be sent
380 to the syslog.
381
382config DEBUG_HIGHMEM
383 bool "Highmem debugging"
384 depends on DEBUG_KERNEL && HIGHMEM
385 help
386 This options enables addition error checking for high memory systems.
387 Disable for production systems.
388
389config DEBUG_BUGVERBOSE
390 bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
Matt Mackallc8538a72005-05-01 08:59:01 -0700391 depends on BUG
Mike Frysinger529a73f2007-11-23 14:28:44 +0800392 depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || FRV || SUPERH || GENERIC_BUG || BLACKFIN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393 default !EMBEDDED
394 help
395 Say Y here to make BUG() panics output the file name and line number
396 of the BUG call as well as the EIP and oops trace. This aids
397 debugging but costs about 70-100K of memory.
398
399config DEBUG_INFO
400 bool "Compile the kernel with debug info"
401 depends on DEBUG_KERNEL
402 help
403 If you say Y here the resulting kernel image will include
404 debugging info resulting in a larger kernel image.
Andreas Dilgerb72e53f2007-03-27 15:21:33 -0600405 This adds debug symbols to the kernel and modules (gcc -g), and
406 is needed if you intend to use kernel crashdump or binary object
407 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700408 Say Y here only if you plan to debug the kernel.
409
410 If unsure, say N.
411
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800412config DEBUG_VM
413 bool "Debug VM"
414 depends on DEBUG_KERNEL
415 help
Nick Piggin13e74442006-01-06 00:10:58 -0800416 Enable this to turn on extended checks in the virtual-memory system
417 that may impact performance.
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800418
419 If unsure, say N.
420
Dave Jones199a9af2006-09-29 01:59:00 -0700421config DEBUG_LIST
422 bool "Debug linked list manipulation"
423 depends on DEBUG_KERNEL
424 help
425 Enable this to turn on extended checks in the linked-list
426 walking routines.
427
428 If unsure, say N.
429
Jens Axboed6ec0842007-10-22 20:01:06 +0200430config DEBUG_SG
431 bool "Debug SG table operations"
432 depends on DEBUG_KERNEL
433 help
434 Enable this to turn on checks on scatter-gather tables. This can
435 help find problems with drivers that do not properly initialize
436 their sg tables.
437
438 If unsure, say N.
439
Linus Torvalds1da177e2005-04-16 15:20:36 -0700440config FRAME_POINTER
441 bool "Compile the kernel with frame pointers"
Mike Frysinger529a73f2007-11-23 14:28:44 +0800442 depends on DEBUG_KERNEL && (X86 || CRIS || M68K || M68KNOMMU || FRV || UML || S390 || AVR32 || SUPERH || BLACKFIN)
Paolo 'Blaisorblade' Giarrusso37fce852005-05-28 15:51:59 -0700443 default y if DEBUG_INFO && UML
Linus Torvalds1da177e2005-04-16 15:20:36 -0700444 help
445 If you say Y here the resulting kernel image will be slightly larger
Jesper Juhl2a38bcc2005-10-30 15:02:51 -0800446 and slower, but it might give very useful debugging information on
447 some architectures or if you use external debuggers.
Andi Kleenaeb39982005-09-12 18:49:25 +0200448 If you don't debug the kernel, you can say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700449
Ingo Molnara9df3d02006-01-14 13:21:33 -0800450config FORCED_INLINING
451 bool "Force gcc to inline functions marked 'inline'"
452 depends on DEBUG_KERNEL
453 default y
454 help
455 This option determines if the kernel forces gcc to inline the functions
456 developers have marked 'inline'. Doing so takes away freedom from gcc to
457 do what it thinks is best, which is desirable for the gcc 3.x series of
458 compilers. The gcc 4.x series have a rewritten inlining algorithm and
459 disabling this option will generate a smaller kernel there. Hopefully
460 this algorithm is so good that allowing gcc4 to make the decision can
461 become the default in the future, until then this option is there to
462 test gcc for this.
463
Randy Dunlapbfe8df32007-10-16 01:23:46 -0700464config BOOT_PRINTK_DELAY
465 bool "Delay each boot printk message by N milliseconds"
466 depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY
467 help
468 This build option allows you to read kernel boot messages
469 by inserting a short delay after each one. The delay is
470 specified in milliseconds on the kernel command line,
471 using "boot_delay=N".
472
473 It is likely that you would also need to use "lpj=M" to preset
474 the "loops per jiffie" value.
475 See a previous boot log for the "lpj" value to use for your
476 system, and then set "lpj=M" before setting "boot_delay=N".
477 NOTE: Using this option may adversely affect SMP systems.
478 I.e., processors other than the first one may not boot up.
479 BOOT_PRINTK_DELAY also may cause DETECT_SOFTLOCKUP to detect
480 what it believes to be lockup conditions.
481
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800482config RCU_TORTURE_TEST
483 tristate "torture tests for RCU"
484 depends on DEBUG_KERNEL
Paul E. McKenney9aaffc82007-05-23 13:57:41 -0700485 depends on m
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800486 default n
487 help
488 This option provides a kernel module that runs torture tests
489 on the RCU infrastructure. The kernel module may be built
490 after the fact on the running kernel to be tested, if desired.
491
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800492 Say M if you want the RCU torture tests to build as a module.
493 Say N if you are unsure.
Ankita Garg8bb31b92006-10-02 02:17:36 -0700494
495config LKDTM
496 tristate "Linux Kernel Dump Test Tool Module"
Don Mullisbf4735a2006-12-10 02:18:37 -0800497 depends on DEBUG_KERNEL
Ankita Garg8bb31b92006-10-02 02:17:36 -0700498 depends on KPROBES
499 default n
500 help
501 This module enables testing of the different dumping mechanisms by
502 inducing system failures at predefined crash points.
503 If you don't need it: say N
504 Choose M here to compile this code as a module. The module will be
505 called lkdtm.
506
507 Documentation on how to use the module can be found in
508 drivers/misc/lkdtm.c
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800509
510config FAULT_INJECTION
Andrew Morton1ab85092006-12-08 02:39:49 -0800511 bool "Fault-injection framework"
512 depends on DEBUG_KERNEL
Akinobu Mita329409a2006-12-08 02:39:48 -0800513 help
514 Provide fault-injection framework.
515 For more details, see Documentation/fault-injection/.
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800516
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800517config FAILSLAB
Andrew Morton1ab85092006-12-08 02:39:49 -0800518 bool "Fault-injection capability for kmalloc"
519 depends on FAULT_INJECTION
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800520 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800521 Provide fault-injection capability for kmalloc.
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800522
Akinobu Mita933e3122006-12-08 02:39:45 -0800523config FAIL_PAGE_ALLOC
524 bool "Fault-injection capabilitiy for alloc_pages()"
Andrew Morton1ab85092006-12-08 02:39:49 -0800525 depends on FAULT_INJECTION
Akinobu Mita933e3122006-12-08 02:39:45 -0800526 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800527 Provide fault-injection capability for alloc_pages().
Akinobu Mita933e3122006-12-08 02:39:45 -0800528
Akinobu Mitac17bb492006-12-08 02:39:46 -0800529config FAIL_MAKE_REQUEST
Dave Jones86327d12006-12-12 20:16:36 +0100530 bool "Fault-injection capability for disk IO"
Andrew Morton1ab85092006-12-08 02:39:49 -0800531 depends on FAULT_INJECTION
Akinobu Mitac17bb492006-12-08 02:39:46 -0800532 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800533 Provide fault-injection capability for disk IO.
Akinobu Mitac17bb492006-12-08 02:39:46 -0800534
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800535config FAULT_INJECTION_DEBUG_FS
536 bool "Debugfs entries for fault-injection capabilities"
Andrew Morton1ab85092006-12-08 02:39:49 -0800537 depends on FAULT_INJECTION && SYSFS && DEBUG_FS
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800538 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800539 Enable configuration of fault-injection capabilities via debugfs.
Akinobu Mita1df49002007-02-20 13:57:56 -0800540
541config FAULT_INJECTION_STACKTRACE_FILTER
542 bool "stacktrace filter for fault-injection capabilities"
543 depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
Akinobu Mita6d690dc2007-05-12 10:36:53 -0700544 depends on !X86_64
Akinobu Mita1df49002007-02-20 13:57:56 -0800545 select STACKTRACE
546 select FRAME_POINTER
547 help
548 Provide stacktrace filter for fault-injection capabilities
Mathieu Desnoyers267c4022007-10-18 23:41:07 -0700549
Arjan van de Ven97455122008-01-25 21:08:34 +0100550config LATENCYTOP
551 bool "Latency measuring infrastructure"
552 select FRAME_POINTER if !MIPS
553 select KALLSYMS
554 select KALLSYMS_ALL
555 select STACKTRACE
556 select SCHEDSTATS
557 select SCHED_DEBUG
558 depends on X86 || X86_64
559 help
560 Enable this option if you want to use the LatencyTOP tool
561 to find out which userspace is blocking on what kernel operations.
562
563
Mathieu Desnoyers267c4022007-10-18 23:41:07 -0700564source "samples/Kconfig"