blob: e85d549b6eac20eb040ba4b27d6f4d334e0b5106 [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
Andi Kleen35bb5b12008-02-22 15:15:03 +010028config FRAME_WARN
29 int "Warn for stack frames larger than (needs gcc 4.4)"
30 range 0 8192
31 default 1024 if !64BIT
32 default 2048 if 64BIT
33 help
34 Tell gcc to warn at build time for stack frames larger than this.
35 Setting this too low will cause a lot of warnings.
36 Setting it to 0 disables the warning.
37 Requires gcc 4.4
38
Linus Torvalds1da177e2005-04-16 15:20:36 -070039config MAGIC_SYSRQ
40 bool "Magic SysRq key"
Adrian Bunkf346f4b2006-01-09 20:54:51 -080041 depends on !UML
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 If you say Y here, you will have some control over the system even
44 if the system crashes for example during kernel debugging (e.g., you
45 will be able to flush the buffer cache to disk, reboot the system
46 immediately or dump some status information). This is accomplished
47 by pressing various keys while holding SysRq (Alt+PrintScreen). It
48 also works on a serial console (on PC hardware at least), if you
49 send a BREAK and then within 5 seconds a command keypress. The
50 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
51 unless you really know what this hack does.
52
Randy Dunlap99657c72009-09-18 12:49:22 -070053config STRIP_ASM_SYMS
54 bool "Strip assembler-generated symbols during link"
55 default n
56 help
57 Strip internal assembler-generated symbols during a link (symbols
58 that look like '.Lxxx') so they don't pollute the output of
59 get_wchan() and suchlike.
60
Arjan van de Venf71d20e2006-06-28 04:26:45 -070061config UNUSED_SYMBOLS
62 bool "Enable unused/obsolete exported symbols"
63 default y if X86
64 help
65 Unused but exported symbols make the kernel needlessly bigger. For
66 that reason most of these unused exports will soon be removed. This
67 option is provided temporarily to provide a transition period in case
68 some external kernel module needs one of these symbols anyway. If you
69 encounter such a case in your module, consider if you are actually
70 using the right API. (rationale: since nobody in the kernel is using
71 this in a module, there is a pretty good chance it's actually the
72 wrong interface to use). If you really need the symbol, please send a
73 mail to the linux kernel mailing list mentioning the symbol and why
74 you really need it, and what the merge plan to the mainline kernel for
75 your module is.
76
Don Mullisbf4735a2006-12-10 02:18:37 -080077config DEBUG_FS
78 bool "Debug Filesystem"
Don Mullisbf4735a2006-12-10 02:18:37 -080079 help
80 debugfs is a virtual file system that kernel developers use to put
81 debugging files into. Enable this option to be able to read and
82 write to these files.
83
Robert P. J. Dayff543332008-05-20 00:06:00 +020084 For detailed documentation on the debugfs API, see
85 Documentation/DocBook/filesystems.
86
Don Mullisbf4735a2006-12-10 02:18:37 -080087 If unsure, say N.
88
89config HEADERS_CHECK
90 bool "Run 'make headers_check' when building vmlinux"
91 depends on !UML
92 help
93 This option will extract the user-visible kernel headers whenever
94 building the kernel, and will run basic sanity checks on them to
95 ensure that exported files do not attempt to include files which
96 were not exported, etc.
97
98 If you're making modifications to header files which are
99 relevant for userspace, say 'Y', and check the headers
100 exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
101 your build tree), to make sure they're suitable.
102
Sam Ravnborg91341d42008-01-21 21:31:44 +0100103config DEBUG_SECTION_MISMATCH
104 bool "Enable full Section mismatch analysis"
Mike Frysinger1d536612010-03-23 13:35:17 -0700105 depends on UNDEFINED || (BLACKFIN)
106 default y
Sam Ravnborgfa2144b2008-02-15 13:53:11 +0100107 # This option is on purpose disabled for now.
André Goddard Rosaaf901ca2009-11-14 13:09:05 -0200108 # It will be enabled when we are down to a reasonable number
Sam Ravnborgfa2144b2008-02-15 13:53:11 +0100109 # of section mismatch warnings (< 10 for an allyesconfig build)
Sam Ravnborg91341d42008-01-21 21:31:44 +0100110 help
111 The section mismatch analysis checks if there are illegal
112 references from one section to another section.
113 Linux will during link or during runtime drop some sections
114 and any use of code/data previously in these sections will
115 most likely result in an oops.
116 In the code functions and variables are annotated with
117 __init, __devinit etc. (see full list in include/linux/init.h)
Geert Uytterhoevend6fbfa42008-01-30 11:13:23 +0100118 which results in the code/data being placed in specific sections.
119 The section mismatch analysis is always done after a full
120 kernel build but enabling this option will in addition
Sam Ravnborg91341d42008-01-21 21:31:44 +0100121 do the following:
122 - Add the option -fno-inline-functions-called-once to gcc
123 When inlining a function annotated __init in a non-init
Geert Uytterhoevend6fbfa42008-01-30 11:13:23 +0100124 function we would lose the section information and thus
Sam Ravnborg91341d42008-01-21 21:31:44 +0100125 the analysis would not catch the illegal reference.
Geert Uytterhoevend6fbfa42008-01-30 11:13:23 +0100126 This option tells gcc to inline less but will also
Sam Ravnborg91341d42008-01-21 21:31:44 +0100127 result in a larger kernel.
128 - Run the section mismatch analysis for each module/built-in.o
129 When we run the section mismatch analysis on vmlinux.o we
Geert Uytterhoevend6fbfa42008-01-30 11:13:23 +0100130 lose valueble information about where the mismatch was
Sam Ravnborg91341d42008-01-21 21:31:44 +0100131 introduced.
132 Running the analysis for each module/built-in.o file
133 will tell where the mismatch happens much closer to the
134 source. The drawback is that we will report the same
135 mismatch at least twice.
Sam Ravnborg588ccd72008-01-24 21:12:37 +0100136 - Enable verbose reporting from modpost to help solving
137 the section mismatches reported.
Sam Ravnborg91341d42008-01-21 21:31:44 +0100138
Adrian Bunkf346f4b2006-01-09 20:54:51 -0800139config DEBUG_KERNEL
140 bool "Kernel debugging"
141 help
142 Say Y here if you are developing drivers or trying to debug and
143 identify kernel problems.
144
David Woodhousea304e1b2007-02-12 00:52:00 -0800145config DEBUG_SHIRQ
146 bool "Debug shared IRQ handlers"
147 depends on DEBUG_KERNEL && GENERIC_HARDIRQS
148 help
149 Enable this to generate a spurious interrupt as soon as a shared
150 interrupt handler is registered, and just before one is deregistered.
151 Drivers ought to be able to handle interrupts coming in at those
152 points; some don't and need to be caught.
153
Don Zickus58687ac2010-05-07 17:11:44 -0400154config LOCKUP_DETECTOR
155 bool "Detect Hard and Soft Lockups"
Heiko Carstensdea20a32006-10-11 01:20:44 -0700156 depends on DEBUG_KERNEL && !S390
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700157 help
Don Zickus58687ac2010-05-07 17:11:44 -0400158 Say Y here to enable the kernel to act as a watchdog to detect
159 hard and soft lockups.
Don Zickus84e478c2010-02-05 21:47:05 -0500160
Don Zickus58687ac2010-05-07 17:11:44 -0400161 Softlockups are bugs that cause the kernel to loop in kernel
Ingo Molnar9c44bc02008-05-12 21:21:04 +0200162 mode for more than 60 seconds, without giving other tasks a
Don Zickus58687ac2010-05-07 17:11:44 -0400163 chance to run. The current stack trace is displayed upon
164 detection and the system will stay locked up.
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700165
Don Zickus58687ac2010-05-07 17:11:44 -0400166 Hardlockups are bugs that cause the CPU to loop in kernel mode
167 for more than 60 seconds, without letting other interrupts have a
168 chance to run. The current stack trace is displayed upon detection
169 and the system will stay locked up.
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700170
Don Zickus58687ac2010-05-07 17:11:44 -0400171 The overhead should be minimal. A periodic hrtimer runs to
172 generate interrupts and kick the watchdog task every 10-12 seconds.
173 An NMI is generated every 60 seconds or so to check for hardlockups.
Don Zickus84e478c2010-02-05 21:47:05 -0500174
Frederic Weisbecker23637d42010-05-15 23:15:20 +0200175config HARDLOCKUP_DETECTOR
176 def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI
Ingo Molnar8446f1d2005-09-06 15:16:27 -0700177
Ingo Molnar9c44bc02008-05-12 21:21:04 +0200178config BOOTPARAM_SOFTLOCKUP_PANIC
179 bool "Panic (Reboot) On Soft Lockups"
Frederic Weisbecker89d7ce22010-05-13 00:27:20 +0200180 depends on LOCKUP_DETECTOR
Ingo Molnar9c44bc02008-05-12 21:21:04 +0200181 help
182 Say Y here to enable the kernel to panic on "soft lockups",
183 which are bugs that cause the kernel to loop in kernel
184 mode for more than 60 seconds, without giving other tasks a
185 chance to run.
186
187 The panic can be used in combination with panic_timeout,
188 to cause the system to reboot automatically after a
189 lockup has been detected. This feature is useful for
190 high-availability systems that have uptime guarantees and
191 where a lockup must be resolved ASAP.
192
193 Say N if unsure.
194
195config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
196 int
Frederic Weisbeckere16bb1d2010-05-15 22:30:22 +0200197 depends on LOCKUP_DETECTOR
Ingo Molnar9c44bc02008-05-12 21:21:04 +0200198 range 0 1
199 default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC
200 default 1 if BOOTPARAM_SOFTLOCKUP_PANIC
201
Mandeep Singh Bainese162b392009-01-15 11:08:40 -0800202config DETECT_HUNG_TASK
203 bool "Detect Hung Tasks"
204 depends on DEBUG_KERNEL
Ingo Molnar77d05632009-04-07 08:55:36 +0200205 default DETECT_SOFTLOCKUP
Mandeep Singh Bainese162b392009-01-15 11:08:40 -0800206 help
207 Say Y here to enable the kernel to detect "hung tasks",
208 which are bugs that cause the task to be stuck in
209 uninterruptible "D" state indefinitiley.
210
211 When a hung task is detected, the kernel will print the
212 current stack trace (which you should report), but the
213 task will stay in uninterruptible state. If lockdep is
214 enabled then all held locks will also be reported. This
215 feature has negligible overhead.
216
217config BOOTPARAM_HUNG_TASK_PANIC
218 bool "Panic (Reboot) On Hung Tasks"
219 depends on DETECT_HUNG_TASK
220 help
221 Say Y here to enable the kernel to panic on "hung tasks",
222 which are bugs that cause the kernel to leave a task stuck
223 in uninterruptible "D" state.
224
225 The panic can be used in combination with panic_timeout,
226 to cause the system to reboot automatically after a
227 hung task has been detected. This feature is useful for
228 high-availability systems that have uptime guarantees and
229 where a hung tasks must be resolved ASAP.
230
231 Say N if unsure.
232
233config BOOTPARAM_HUNG_TASK_PANIC_VALUE
234 int
235 depends on DETECT_HUNG_TASK
236 range 0 1
237 default 0 if !BOOTPARAM_HUNG_TASK_PANIC
238 default 1 if BOOTPARAM_HUNG_TASK_PANIC
239
Ingo Molnarb642b6d2007-07-09 18:52:00 +0200240config SCHED_DEBUG
241 bool "Collect scheduler debugging info"
242 depends on DEBUG_KERNEL && PROC_FS
243 default y
244 help
245 If you say Y here, the /proc/sched_debug file will be provided
246 that can help debug the scheduler. The runtime overhead of this
247 option is minimal.
248
Linus Torvalds1da177e2005-04-16 15:20:36 -0700249config SCHEDSTATS
250 bool "Collect scheduler statistics"
251 depends on DEBUG_KERNEL && PROC_FS
252 help
253 If you say Y here, additional code will be inserted into the
254 scheduler and related routines to collect statistics about
255 scheduler behavior and provide them in /proc/schedstat. These
256 stats may be useful for both tuning and debugging the scheduler
257 If you aren't debugging the scheduler or trying to tune a specific
258 application, you can say N to avoid the very slight overhead
259 this adds.
260
Ingo Molnar82f67cd2007-02-16 01:28:13 -0800261config TIMER_STATS
262 bool "Collect kernel timers statistics"
263 depends on DEBUG_KERNEL && PROC_FS
264 help
265 If you say Y here, additional code will be inserted into the
266 timer routines to collect statistics about kernel timers being
267 reprogrammed. The statistics can be read from /proc/timer_stats.
268 The statistics collection is started by writing 1 to /proc/timer_stats,
269 writing 0 stops it. This feature is useful to collect information
Ingo Molnarc1a834d2007-06-01 00:47:16 -0700270 about timer usage patterns in kernel and userspace. This feature
271 is lightweight if enabled in the kernel config but not activated
272 (it defaults to deactivated on bootup and will only be activated
273 if some application like powertop activates it explicitly).
Ingo Molnar82f67cd2007-02-16 01:28:13 -0800274
Thomas Gleixner3ac7fe52008-04-30 00:55:01 -0700275config DEBUG_OBJECTS
276 bool "Debug object operations"
277 depends on DEBUG_KERNEL
278 help
279 If you say Y here, additional code will be inserted into the
280 kernel to track the life time of various objects and validate
281 the operations on those objects.
282
283config DEBUG_OBJECTS_SELFTEST
284 bool "Debug objects selftest"
285 depends on DEBUG_OBJECTS
286 help
287 This enables the selftest of the object debug code.
288
289config DEBUG_OBJECTS_FREE
290 bool "Debug objects in freed memory"
291 depends on DEBUG_OBJECTS
292 help
293 This enables checks whether a k/v free operation frees an area
294 which contains an object which has not been deactivated
295 properly. This can make kmalloc/kfree-intensive workloads
296 much slower.
297
Thomas Gleixnerc6f3a972008-04-30 00:55:03 -0700298config DEBUG_OBJECTS_TIMERS
299 bool "Debug timer objects"
300 depends on DEBUG_OBJECTS
301 help
302 If you say Y here, additional code will be inserted into the
303 timer routines to track the life time of timer objects and
304 validate the timer operations.
305
Thomas Gleixnerdc186ad2009-11-16 01:09:48 +0900306config DEBUG_OBJECTS_WORK
307 bool "Debug work objects"
308 depends on DEBUG_OBJECTS
309 help
310 If you say Y here, additional code will be inserted into the
311 work queue routines to track the life time of work objects and
312 validate the work operations.
313
Mathieu Desnoyers551d55a2010-04-17 08:48:42 -0400314config DEBUG_OBJECTS_RCU_HEAD
315 bool "Debug RCU callbacks objects"
316 depends on DEBUG_OBJECTS && PREEMPT
317 help
318 Enable this to turn on debugging of RCU list heads (call_rcu() usage).
319
Ingo Molnar3ae70202008-11-26 10:02:00 +0100320config DEBUG_OBJECTS_ENABLE_DEFAULT
321 int "debug_objects bootup default value (0-1)"
322 range 0 1
323 default "1"
324 depends on DEBUG_OBJECTS
325 help
326 Debug objects boot parameter default value
327
Linus Torvalds1da177e2005-04-16 15:20:36 -0700328config DEBUG_SLAB
Andrew Morton4a2f0ac2006-03-25 03:07:22 -0800329 bool "Debug slab memory allocations"
Vegard Nossum7d46d9e2008-04-04 00:51:41 +0200330 depends on DEBUG_KERNEL && SLAB && !KMEMCHECK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700331 help
332 Say Y here to have the kernel do limited verification on memory
333 allocation as well as poisoning memory on free to catch use of freed
334 memory. This can make kmalloc/kfree-intensive workloads much slower.
335
Al Viro871751e2006-03-25 03:06:39 -0800336config DEBUG_SLAB_LEAK
337 bool "Memory leak debugging"
338 depends on DEBUG_SLAB
339
Christoph Lameterf0630ff2007-07-15 23:38:14 -0700340config SLUB_DEBUG_ON
341 bool "SLUB debugging on by default"
Vegard Nossum7d46d9e2008-04-04 00:51:41 +0200342 depends on SLUB && SLUB_DEBUG && !KMEMCHECK
Christoph Lameterf0630ff2007-07-15 23:38:14 -0700343 default n
344 help
345 Boot with debugging on by default. SLUB boots by default with
346 the runtime debug capabilities switched off. Enabling this is
347 equivalent to specifying the "slub_debug" parameter on boot.
348 There is no support for more fine grained debug control like
349 possible with slub_debug=xxx. SLUB debugging may be switched
350 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
351 "slub_debug=-".
352
Christoph Lameter8ff12cf2008-02-07 17:47:41 -0800353config SLUB_STATS
354 default n
355 bool "Enable SLUB performance statistics"
Christoph Lameter5b06c8532008-04-14 18:51:34 +0300356 depends on SLUB && SLUB_DEBUG && SYSFS
Christoph Lameter8ff12cf2008-02-07 17:47:41 -0800357 help
358 SLUB statistics are useful to debug SLUBs allocation behavior in
359 order find ways to optimize the allocator. This should never be
360 enabled for production use since keeping statistics slows down
361 the allocator by a few percentage points. The slabinfo command
362 supports the determination of the most active slabs to figure
363 out which slabs are relevant to a particular load.
364 Try running: slabinfo -DA
365
Catalin Marinas3bba00d2009-06-11 13:24:13 +0100366config DEBUG_KMEMLEAK
367 bool "Kernel memory leak detector"
Heiko Carstensdfcc3e62009-10-06 10:33:57 +0200368 depends on DEBUG_KERNEL && EXPERIMENTAL && !MEMORY_HOTPLUG && \
David S. Miller9343af02010-04-13 00:28:45 -0700369 (X86 || ARM || PPC || S390 || SPARC64 || SUPERH || MICROBLAZE)
Heiko Carstensdfcc3e62009-10-06 10:33:57 +0200370
Catalin Marinas3bba00d2009-06-11 13:24:13 +0100371 select DEBUG_FS if SYSFS
372 select STACKTRACE if STACKTRACE_SUPPORT
373 select KALLSYMS
Randy Dunlapb60e26a2009-11-06 15:33:45 -0800374 select CRC32
Catalin Marinas3bba00d2009-06-11 13:24:13 +0100375 help
376 Say Y here if you want to enable the memory leak
377 detector. The memory allocation/freeing is traced in a way
378 similar to the Boehm's conservative garbage collector, the
379 difference being that the orphan objects are not freed but
380 only shown in /sys/kernel/debug/kmemleak. Enabling this
381 feature will introduce an overhead to memory
382 allocations. See Documentation/kmemleak.txt for more
383 details.
384
Catalin Marinasbf96d1e2009-06-23 14:40:27 +0100385 Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances
386 of finding leaks due to the slab objects poisoning.
387
Catalin Marinas3bba00d2009-06-11 13:24:13 +0100388 In order to access the kmemleak file, debugfs needs to be
389 mounted (usually at /sys/kernel/debug).
390
Catalin Marinasa9d90582009-06-25 10:16:11 +0100391config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
392 int "Maximum kmemleak early log entries"
393 depends on DEBUG_KMEMLEAK
Heiko Carstensdfcc3e62009-10-06 10:33:57 +0200394 range 200 40000
Catalin Marinasa9d90582009-06-25 10:16:11 +0100395 default 400
396 help
397 Kmemleak must track all the memory allocations to avoid
398 reporting false positives. Since memory may be allocated or
399 freed before kmemleak is initialised, an early log buffer is
400 used to store these actions. If kmemleak reports "early log
401 buffer exceeded", please increase this value.
402
Catalin Marinas0822ee42009-06-11 13:24:14 +0100403config DEBUG_KMEMLEAK_TEST
404 tristate "Simple test for the kernel memory leak detector"
405 depends on DEBUG_KMEMLEAK
406 help
407 Say Y or M here to build a test for the kernel memory leak
408 detector. This option enables a module that explicitly leaks
409 memory.
410
411 If unsure, say N.
412
Jason Baronab0155a2010-07-19 11:54:17 +0100413config DEBUG_KMEMLEAK_DEFAULT_OFF
414 bool "Default kmemleak to off"
415 depends on DEBUG_KMEMLEAK
416 help
417 Say Y here to disable kmemleak by default. It can then be enabled
418 on the command line via kmemleak=on.
419
Linus Torvalds1da177e2005-04-16 15:20:36 -0700420config DEBUG_PREEMPT
421 bool "Debug preemptible kernel"
Kumar Gala01deab92009-10-16 07:21:39 +0000422 depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700423 default y
424 help
425 If you say Y here then the kernel will use a debug variant of the
426 commonly used smp_processor_id() function and will print warnings
427 if kernel code uses it in a preemption-unsafe way. Also, the kernel
428 will detect preemption count underflows.
429
Ingo Molnare7eebaf2006-06-27 02:54:55 -0700430config DEBUG_RT_MUTEXES
431 bool "RT Mutex debugging, deadlock detection"
Ingo Molnare7eebaf2006-06-27 02:54:55 -0700432 depends on DEBUG_KERNEL && RT_MUTEXES
433 help
434 This allows rt mutex semantics violations and rt mutex related
435 deadlocks (lockups) to be detected and reported automatically.
436
437config DEBUG_PI_LIST
438 bool
439 default y
440 depends on DEBUG_RT_MUTEXES
441
Thomas Gleixner61a87122006-06-27 02:54:56 -0700442config RT_MUTEX_TESTER
443 bool "Built-in scriptable tester for rt-mutexes"
Roman Zippela1583d32006-06-27 02:55:00 -0700444 depends on DEBUG_KERNEL && RT_MUTEXES
Thomas Gleixner61a87122006-06-27 02:54:56 -0700445 help
446 This option enables a rt-mutex tester.
447
Linus Torvalds1da177e2005-04-16 15:20:36 -0700448config DEBUG_SPINLOCK
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700449 bool "Spinlock and rw-lock debugging: basic checks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700450 depends on DEBUG_KERNEL
451 help
452 Say Y here and build SMP to catch missing spinlock initialization
453 and certain other kinds of spinlock errors commonly made. This is
454 best used in conjunction with the NMI watchdog so that spinlock
455 deadlocks are also debuggable.
456
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700457config DEBUG_MUTEXES
458 bool "Mutex debugging: basic checks"
459 depends on DEBUG_KERNEL
460 help
461 This feature allows mutex semantics violations to be detected and
462 reported.
463
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700464config DEBUG_LOCK_ALLOC
465 bool "Lock debugging: detect incorrect freeing of live locks"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700466 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700467 select DEBUG_SPINLOCK
468 select DEBUG_MUTEXES
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700469 select LOCKDEP
470 help
471 This feature will check whether any held lock (spinlock, rwlock,
472 mutex or rwsem) is incorrectly freed by the kernel, via any of the
473 memory-freeing routines (kfree(), kmem_cache_free(), free_pages(),
474 vfree(), etc.), whether a live lock is incorrectly reinitialized via
475 spin_lock_init()/mutex_init()/etc., or whether there is any lock
476 held during task exit.
477
478config PROVE_LOCKING
479 bool "Lock debugging: prove locking correctness"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700480 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700481 select LOCKDEP
482 select DEBUG_SPINLOCK
483 select DEBUG_MUTEXES
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700484 select DEBUG_LOCK_ALLOC
Steven Rostedt46b93b72010-08-31 16:35:20 -0400485 select TRACE_IRQFLAGS
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700486 default n
487 help
488 This feature enables the kernel to prove that all locking
489 that occurs in the kernel runtime is mathematically
490 correct: that under no circumstance could an arbitrary (and
491 not yet triggered) combination of observed locking
492 sequences (on an arbitrary number of CPUs, running an
493 arbitrary number of tasks and interrupt contexts) cause a
494 deadlock.
495
496 In short, this feature enables the kernel to report locking
497 related deadlocks before they actually occur.
498
499 The proof does not depend on how hard and complex a
500 deadlock scenario would be to trigger: how many
501 participant CPUs, tasks and irq-contexts would be needed
502 for it to trigger. The proof also does not depend on
503 timing: if a race and a resulting deadlock is possible
504 theoretically (no matter how unlikely the race scenario
505 is), it will be proven so and will immediately be
506 reported by the kernel (once the event is observed that
507 makes the deadlock theoretically possible).
508
509 If a deadlock is impossible (i.e. the locking rules, as
510 observed by the kernel, are mathematically correct), the
511 kernel reports nothing.
512
513 NOTE: this feature can also be enabled for rwlocks, mutexes
514 and rwsems - in which case all dependencies between these
515 different locking variants are observed and mapped too, and
516 the proof of observed correctness is also maintained for an
517 arbitrary combination of these separate locking variants.
518
519 For more details, see Documentation/lockdep-design.txt.
520
Paul E. McKenney632ee202010-02-22 17:04:45 -0800521config PROVE_RCU
522 bool "RCU debugging: prove RCU correctness"
523 depends on PROVE_LOCKING
524 default n
525 help
526 This feature enables lockdep extensions that check for correct
527 use of RCU APIs. This is currently under development. Say Y
528 if you want to debug RCU usage or help work on the PROVE_RCU
529 feature.
530
531 Say N if you are unsure.
532
Lai Jiangshan2b3fc352010-04-20 16:23:07 +0800533config PROVE_RCU_REPEATEDLY
534 bool "RCU debugging: don't disable PROVE_RCU on first splat"
535 depends on PROVE_RCU
536 default n
537 help
538 By itself, PROVE_RCU will disable checking upon issuing the
539 first warning (or "splat"). This feature prevents such
540 disabling, allowing multiple RCU-lockdep warnings to be printed
541 on a single reboot.
542
543 Say N if you are unsure.
544
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700545config LOCKDEP
546 bool
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700547 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700548 select STACKTRACE
Michal Simek79aac882010-05-25 11:33:26 +0200549 select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700550 select KALLSYMS
551 select KALLSYMS_ALL
552
Peter Zijlstraf20786f2007-07-19 01:48:56 -0700553config LOCK_STAT
Danny ter Haarfdfb8702007-09-24 21:24:43 -0700554 bool "Lock usage statistics"
Peter Zijlstraf20786f2007-07-19 01:48:56 -0700555 depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
556 select LOCKDEP
557 select DEBUG_SPINLOCK
558 select DEBUG_MUTEXES
559 select DEBUG_LOCK_ALLOC
560 default n
561 help
562 This feature enables tracking lock contention points
563
Peter Zijlstraa560aa42007-10-07 00:24:33 -0700564 For more details, see Documentation/lockstat.txt
565
Frederic Weisbeckerdd8b1cf2010-02-27 17:10:39 +0100566 This also enables lock events required by "perf lock",
567 subcommand of perf.
568 If you want to use "perf lock", you also need to turn on
569 CONFIG_EVENT_TRACING.
Hitoshi Mitake84c6f882010-02-04 16:08:15 +0900570
571 CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
Frederic Weisbeckerdd8b1cf2010-02-27 17:10:39 +0100572 (CONFIG_LOCKDEP defines "acquire" and "release" events.)
Hitoshi Mitake84c6f882010-02-04 16:08:15 +0900573
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700574config DEBUG_LOCKDEP
575 bool "Lock dependency engine debugging"
Adrian Bunk517e7aa2006-07-14 00:24:32 -0700576 depends on DEBUG_KERNEL && LOCKDEP
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700577 help
578 If you say Y here, the lock dependency engine will do
579 additional runtime checks to debug itself, at the price
580 of more runtime overhead.
581
582config TRACE_IRQFLAGS
583 bool
Steven Rostedt46b93b72010-08-31 16:35:20 -0400584 help
585 Enables hooks to interrupt enabling and disabling for
586 either tracing or lock debugging.
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700587
Linus Torvalds1da177e2005-04-16 15:20:36 -0700588config DEBUG_SPINLOCK_SLEEP
Ingo Molnar4d9f34a2006-07-03 00:24:55 -0700589 bool "Spinlock debugging: sleep-inside-spinlock checking"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700590 depends on DEBUG_KERNEL
591 help
592 If you say Y here, various routines which may sleep will become very
593 noisy if they are called with a spinlock held.
594
Ingo Molnarcae2ed92006-07-03 00:24:48 -0700595config DEBUG_LOCKING_API_SELFTESTS
596 bool "Locking API boot-time self-tests"
597 depends on DEBUG_KERNEL
598 help
599 Say Y here if you want the kernel to run a short self-test during
600 bootup. The self-test checks whether common types of locking bugs
601 are detected by debugging mechanisms or not. (if you disable
602 lock debugging then those bugs wont be detected of course.)
603 The following locking APIs are covered: spinlocks, rwlocks,
604 mutexes and rwsems.
605
Ingo Molnar8637c092006-07-03 00:24:38 -0700606config STACKTRACE
607 bool
608 depends on STACKTRACE_SUPPORT
609
Linus Torvalds1da177e2005-04-16 15:20:36 -0700610config DEBUG_KOBJECT
611 bool "kobject debugging"
612 depends on DEBUG_KERNEL
613 help
614 If you say Y here, some extra kobject debugging messages will be sent
615 to the syslog.
616
617config DEBUG_HIGHMEM
618 bool "Highmem debugging"
619 depends on DEBUG_KERNEL && HIGHMEM
620 help
621 This options enables addition error checking for high memory systems.
622 Disable for production systems.
623
624config DEBUG_BUGVERBOSE
625 bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
Matt Mackallc8538a72005-05-01 08:59:01 -0700626 depends on BUG
David Howellsb920de12008-02-08 04:19:31 -0800627 depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \
628 FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300
Alexey Dobriyan8420e7e2009-12-14 18:00:25 -0800629 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700630 help
631 Say Y here to make BUG() panics output the file name and line number
632 of the BUG call as well as the EIP and oops trace. This aids
633 debugging but costs about 70-100K of memory.
634
635config DEBUG_INFO
636 bool "Compile the kernel with debug info"
637 depends on DEBUG_KERNEL
638 help
639 If you say Y here the resulting kernel image will include
640 debugging info resulting in a larger kernel image.
Andreas Dilgerb72e53f2007-03-27 15:21:33 -0600641 This adds debug symbols to the kernel and modules (gcc -g), and
642 is needed if you intend to use kernel crashdump or binary object
643 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700644 Say Y here only if you plan to debug the kernel.
645
646 If unsure, say N.
647
Andi Kleend6f4ceb2010-07-14 15:43:52 +0200648config DEBUG_INFO_REDUCED
649 bool "Reduce debugging information"
650 depends on DEBUG_INFO
651 help
652 If you say Y here gcc is instructed to generate less debugging
653 information for structure types. This means that tools that
654 need full debugging information (like kgdb or systemtap) won't
655 be happy. But if you merely need debugging information to
656 resolve line numbers there is no loss. Advantage is that
657 build directory object sizes shrink dramatically over a full
658 DEBUG_INFO build and compile times are reduced too.
659 Only works with newer gcc versions.
660
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800661config DEBUG_VM
662 bool "Debug VM"
663 depends on DEBUG_KERNEL
664 help
Nick Piggin13e74442006-01-06 00:10:58 -0800665 Enable this to turn on extended checks in the virtual-memory system
666 that may impact performance.
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800667
668 If unsure, say N.
669
Jiri Slaby59ea7462008-06-12 13:56:40 +0200670config DEBUG_VIRTUAL
671 bool "Debug VM translations"
672 depends on DEBUG_KERNEL && X86
673 help
674 Enable some costly sanity checks in virtual to page code. This can
675 catch mistakes with virt_to_page() and friends.
676
677 If unsure, say N.
678
David Howells8feae132009-01-08 12:04:47 +0000679config DEBUG_NOMMU_REGIONS
680 bool "Debug the global anon/private NOMMU mapping region tree"
681 depends on DEBUG_KERNEL && !MMU
682 help
683 This option causes the global tree of anonymous and private mapping
684 regions to be regularly checked for invalid topology.
685
Dave Hansenad775f52008-02-15 14:38:01 -0800686config DEBUG_WRITECOUNT
687 bool "Debug filesystem writers count"
688 depends on DEBUG_KERNEL
689 help
690 Enable this to catch wrong use of the writers count in struct
691 vfsmount. This will increase the size of each file struct by
692 32 bits.
693
694 If unsure, say N.
695
Mel Gorman6b74ab92008-07-23 21:26:49 -0700696config DEBUG_MEMORY_INIT
697 bool "Debug memory initialisation" if EMBEDDED
698 default !EMBEDDED
699 help
700 Enable this for additional checks during memory initialisation.
701 The sanity checks verify aspects of the VM such as the memory model
702 and other information provided by the architecture. Verbose
703 information will be printed at KERN_DEBUG loglevel depending
704 on the mminit_loglevel= command-line option.
705
706 If unsure, say Y
707
Dave Jones199a9af2006-09-29 01:59:00 -0700708config DEBUG_LIST
709 bool "Debug linked list manipulation"
710 depends on DEBUG_KERNEL
711 help
712 Enable this to turn on extended checks in the linked-list
713 walking routines.
714
715 If unsure, say N.
716
Jens Axboed6ec0842007-10-22 20:01:06 +0200717config DEBUG_SG
718 bool "Debug SG table operations"
719 depends on DEBUG_KERNEL
720 help
721 Enable this to turn on checks on scatter-gather tables. This can
722 help find problems with drivers that do not properly initialize
723 their sg tables.
724
725 If unsure, say N.
726
Arjan van de Ven1b2439d2008-08-15 15:29:38 -0700727config DEBUG_NOTIFIERS
728 bool "Debug notifier call chains"
729 depends on DEBUG_KERNEL
730 help
731 Enable this to turn on sanity checking for notifier call chains.
732 This is most useful for kernel developers to make sure that
733 modules properly unregister themselves from notifier chains.
734 This is a relatively cheap check but if you care about maximum
735 performance, say N.
736
David Howellse0e81732009-09-02 09:13:40 +0100737config DEBUG_CREDENTIALS
738 bool "Debug credential management"
739 depends on DEBUG_KERNEL
740 help
741 Enable this to turn on some debug checking for credential
742 management. The additional code keeps track of the number of
743 pointers from task_structs to any given cred struct, and checks to
744 see that this number never exceeds the usage count of the cred
745 struct.
746
747 Furthermore, if SELinux is enabled, this also checks that the
748 security pointer in the cred struct is never seen to be invalid.
749
750 If unsure, say N.
751
Jeff Mahoney64dec402009-01-16 13:23:35 -0500752#
753# Select this config option from the architecture Kconfig, if it
754# it is preferred to always offer frame pointers as a config
755# option on the architecture (regardless of KERNEL_DEBUG):
756#
757config ARCH_WANT_FRAME_POINTERS
758 bool
759 help
760
Linus Torvalds1da177e2005-04-16 15:20:36 -0700761config FRAME_POINTER
762 bool "Compile the kernel with frame pointers"
David Howellsb920de12008-02-08 04:19:31 -0800763 depends on DEBUG_KERNEL && \
Heiko Carstens75ee0342009-04-23 13:58:10 +0200764 (CRIS || M68K || M68KNOMMU || FRV || UML || \
Ingo Molnarda4276b2009-01-07 11:05:10 +0100765 AVR32 || SUPERH || BLACKFIN || MN10300) || \
766 ARCH_WANT_FRAME_POINTERS
767 default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700768 help
Ingo Molnarda4276b2009-01-07 11:05:10 +0100769 If you say Y here the resulting kernel image will be slightly
770 larger and slower, but it gives very useful debugging information
771 in case of kernel bugs. (precise oopses/stacktraces/warnings)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700772
Randy Dunlapbfe8df32007-10-16 01:23:46 -0700773config BOOT_PRINTK_DELAY
774 bool "Delay each boot printk message by N milliseconds"
775 depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY
776 help
777 This build option allows you to read kernel boot messages
778 by inserting a short delay after each one. The delay is
779 specified in milliseconds on the kernel command line,
780 using "boot_delay=N".
781
782 It is likely that you would also need to use "lpj=M" to preset
783 the "loops per jiffie" value.
784 See a previous boot log for the "lpj" value to use for your
785 system, and then set "lpj=M" before setting "boot_delay=N".
786 NOTE: Using this option may adversely affect SMP systems.
787 I.e., processors other than the first one may not boot up.
788 BOOT_PRINTK_DELAY also may cause DETECT_SOFTLOCKUP to detect
789 what it believes to be lockup conditions.
790
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800791config RCU_TORTURE_TEST
792 tristate "torture tests for RCU"
793 depends on DEBUG_KERNEL
794 default n
795 help
796 This option provides a kernel module that runs torture tests
797 on the RCU infrastructure. The kernel module may be built
798 after the fact on the running kernel to be tested, if desired.
799
Paul E. McKenney31a72bc2008-06-18 09:26:49 -0700800 Say Y here if you want RCU torture tests to be built into
801 the kernel.
Paul E. McKenneya241ec62005-10-30 15:03:12 -0800802 Say M if you want the RCU torture tests to build as a module.
803 Say N if you are unsure.
Ankita Garg8bb31b92006-10-02 02:17:36 -0700804
Paul E. McKenney31a72bc2008-06-18 09:26:49 -0700805config RCU_TORTURE_TEST_RUNNABLE
806 bool "torture tests for RCU runnable by default"
807 depends on RCU_TORTURE_TEST = y
808 default n
809 help
810 This option provides a way to build the RCU torture tests
811 directly into the kernel without them starting up at boot
812 time. You can use /proc/sys/kernel/rcutorture_runnable
813 to manually override this setting. This /proc file is
814 available only when the RCU torture tests have been built
815 into the kernel.
816
817 Say Y here if you want the RCU torture tests to start during
818 boot (you probably don't).
819 Say N here if you want the RCU torture tests to start only
820 after being manually enabled via /proc.
821
Paul E. McKenney2133b5d2008-10-02 16:06:39 -0700822config RCU_CPU_STALL_DETECTOR
Paul E. McKenney67182ae2008-08-10 18:35:38 -0700823 bool "Check for stalled CPUs delaying RCU grace periods"
Paul E. McKenney6b3ef482009-08-22 13:56:53 -0700824 depends on TREE_RCU || TREE_PREEMPT_RCU
Paul E. McKenney8bfb2f82009-12-02 12:10:16 -0800825 default y
Paul E. McKenney64db4cf2008-12-18 21:55:32 +0100826 help
827 This option causes RCU to printk information on which
828 CPUs are delaying the current grace period, but only when
829 the grace period extends for excessive time periods.
830
Paul E. McKenney4c540052010-01-14 16:10:57 -0800831 Say N if you want to disable such checks.
Paul E. McKenney64db4cf2008-12-18 21:55:32 +0100832
Paul E. McKenney4c540052010-01-14 16:10:57 -0800833 Say Y if you are unsure.
Paul E. McKenney64db4cf2008-12-18 21:55:32 +0100834
Paul E. McKenney1ed509a2010-02-22 17:05:05 -0800835config RCU_CPU_STALL_VERBOSE
836 bool "Print additional per-task information for RCU_CPU_STALL_DETECTOR"
837 depends on RCU_CPU_STALL_DETECTOR && TREE_PREEMPT_RCU
Paul E. McKenney55ec9362010-04-13 12:22:33 -0700838 default y
Paul E. McKenney1ed509a2010-02-22 17:05:05 -0800839 help
840 This option causes RCU to printk detailed per-task information
841 for any tasks that are stalling the current RCU grace period.
Arjan van de Ven6dab2772008-01-30 13:33:08 +0100842
843 Say N if you are unsure.
844
Paul E. McKenney1ed509a2010-02-22 17:05:05 -0800845 Say Y if you want to enable such checks.
846
Ananth N Mavinakayanahalli8c1c9352008-01-30 13:32:53 +0100847config KPROBES_SANITY_TEST
848 bool "Kprobes sanity tests"
849 depends on DEBUG_KERNEL
850 depends on KPROBES
851 default n
852 help
853 This option provides for testing basic kprobes functionality on
854 boot. A sample kprobe, jprobe and kretprobe are inserted and
855 verified for functionality.
856
857 Say N if you are unsure.
858
Arjan van de Ven6dab2772008-01-30 13:33:08 +0100859config BACKTRACE_SELF_TEST
860 tristate "Self test for the backtrace code"
861 depends on DEBUG_KERNEL
862 default n
863 help
864 This option provides a kernel module that can be used to test
865 the kernel stack backtrace code. This option is not useful
866 for distributions or general kernels, but only for kernel
867 developers working on architecture code.
868
Vegard Nossumad118c52008-06-27 18:04:48 +0200869 Note that if you want to also test saved backtraces, you will
870 have to enable STACKTRACE as well.
871
Arjan van de Ven6dab2772008-01-30 13:33:08 +0100872 Say N if you are unsure.
873
Tejun Heo870d6652008-08-25 19:47:25 +0900874config DEBUG_BLOCK_EXT_DEVT
875 bool "Force extended block device numbers and spread them"
876 depends on DEBUG_KERNEL
877 depends on BLOCK
Jens Axboe759f8ca2008-08-29 09:06:29 +0200878 default n
Tejun Heo870d6652008-08-25 19:47:25 +0900879 help
Tejun Heo0e11e342008-10-13 10:46:01 +0200880 BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
881 SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
882 YOU ARE DOING. Distros, please enable this and fix whatever
883 is broken.
884
Tejun Heo870d6652008-08-25 19:47:25 +0900885 Conventionally, block device numbers are allocated from
886 predetermined contiguous area. However, extended block area
887 may introduce non-contiguous block device numbers. This
888 option forces most block device numbers to be allocated from
889 the extended space and spreads them to discover kernel or
890 userland code paths which assume predetermined contiguous
891 device number allocation.
892
Tejun Heo55dc7db2008-09-01 13:44:35 +0200893 Note that turning on this debug option shuffles all the
894 device numbers for all IDE and SCSI devices including libata
895 ones, so root partition specified using device number
896 directly (via rdev or root=MAJ:MIN) won't work anymore.
897 Textual device names (root=/dev/sdXn) will continue to work.
898
Tejun Heo870d6652008-08-25 19:47:25 +0900899 Say N if you are unsure.
900
Tejun Heo7c756e62009-06-24 15:13:50 +0900901config DEBUG_FORCE_WEAK_PER_CPU
902 bool "Force weak per-cpu definitions"
903 depends on DEBUG_KERNEL
904 help
905 s390 and alpha require percpu variables in modules to be
906 defined weak to work around addressing range issue which
907 puts the following two restrictions on percpu variable
908 definitions.
909
910 1. percpu symbols must be unique whether static or not
911 2. percpu variables can't be defined inside a function
912
913 To ensure that generic code follows the above rules, this
914 option forces all percpu variables to be defined as weak.
915
Ankita Garg8bb31b92006-10-02 02:17:36 -0700916config LKDTM
917 tristate "Linux Kernel Dump Test Tool Module"
Simon Kagstrom0347af42010-03-05 13:42:49 -0800918 depends on DEBUG_FS
Chris Snookfddd9cf2008-02-23 15:23:26 -0800919 depends on BLOCK
Ankita Garg8bb31b92006-10-02 02:17:36 -0700920 default n
921 help
922 This module enables testing of the different dumping mechanisms by
923 inducing system failures at predefined crash points.
924 If you don't need it: say N
925 Choose M here to compile this code as a module. The module will be
926 called lkdtm.
927
928 Documentation on how to use the module can be found in
Simon Kagstrom0347af42010-03-05 13:42:49 -0800929 Documentation/fault-injection/provoke-crashes.txt
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800930
Akinobu Mitac9d221f2010-05-26 14:43:36 -0700931config CPU_NOTIFIER_ERROR_INJECT
932 tristate "CPU notifier error injection module"
933 depends on HOTPLUG_CPU && DEBUG_KERNEL
934 help
935 This option provides a kernel module that can be used to test
936 the error handling of the cpu notifiers
937
938 To compile this code as a module, choose M here: the module will
939 be called cpu-notifier-error-inject.
940
941 If unsure, say N.
942
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800943config FAULT_INJECTION
Andrew Morton1ab85092006-12-08 02:39:49 -0800944 bool "Fault-injection framework"
945 depends on DEBUG_KERNEL
Akinobu Mita329409a2006-12-08 02:39:48 -0800946 help
947 Provide fault-injection framework.
948 For more details, see Documentation/fault-injection/.
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800949
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800950config FAILSLAB
Andrew Morton1ab85092006-12-08 02:39:49 -0800951 bool "Fault-injection capability for kmalloc"
952 depends on FAULT_INJECTION
Akinobu Mita773ff602008-12-23 19:37:01 +0900953 depends on SLAB || SLUB
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800954 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800955 Provide fault-injection capability for kmalloc.
Akinobu Mita8a8b6502006-12-08 02:39:44 -0800956
Akinobu Mita933e3122006-12-08 02:39:45 -0800957config FAIL_PAGE_ALLOC
958 bool "Fault-injection capabilitiy for alloc_pages()"
Andrew Morton1ab85092006-12-08 02:39:49 -0800959 depends on FAULT_INJECTION
Akinobu Mita933e3122006-12-08 02:39:45 -0800960 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800961 Provide fault-injection capability for alloc_pages().
Akinobu Mita933e3122006-12-08 02:39:45 -0800962
Akinobu Mitac17bb492006-12-08 02:39:46 -0800963config FAIL_MAKE_REQUEST
Dave Jones86327d12006-12-12 20:16:36 +0100964 bool "Fault-injection capability for disk IO"
Jens Axboe581d4e22008-09-14 05:56:33 -0700965 depends on FAULT_INJECTION && BLOCK
Akinobu Mitac17bb492006-12-08 02:39:46 -0800966 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800967 Provide fault-injection capability for disk IO.
Akinobu Mitac17bb492006-12-08 02:39:46 -0800968
Jens Axboe581d4e22008-09-14 05:56:33 -0700969config FAIL_IO_TIMEOUT
Takuya Yoshikawaf4d01432010-07-21 16:05:53 +0900970 bool "Fault-injection capability for faking disk interrupts"
Jens Axboe581d4e22008-09-14 05:56:33 -0700971 depends on FAULT_INJECTION && BLOCK
972 help
973 Provide fault-injection capability on end IO handling. This
974 will make the block layer "forget" an interrupt as configured,
975 thus exercising the error handling.
976
977 Only works with drivers that use the generic timeout handling,
978 for others it wont do anything.
979
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800980config FAULT_INJECTION_DEBUG_FS
981 bool "Debugfs entries for fault-injection capabilities"
Andrew Morton1ab85092006-12-08 02:39:49 -0800982 depends on FAULT_INJECTION && SYSFS && DEBUG_FS
Akinobu Mita6ff1cb32006-12-08 02:39:43 -0800983 help
Andrew Morton1ab85092006-12-08 02:39:49 -0800984 Enable configuration of fault-injection capabilities via debugfs.
Akinobu Mita1df49002007-02-20 13:57:56 -0800985
986config FAULT_INJECTION_STACKTRACE_FILTER
987 bool "stacktrace filter for fault-injection capabilities"
988 depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
Akinobu Mita6d690dc2007-05-12 10:36:53 -0700989 depends on !X86_64
Akinobu Mita1df49002007-02-20 13:57:56 -0800990 select STACKTRACE
Michal Simek79aac882010-05-25 11:33:26 +0200991 select FRAME_POINTER if !PPC && !S390 && !MICROBLAZE
Akinobu Mita1df49002007-02-20 13:57:56 -0800992 help
993 Provide stacktrace filter for fault-injection capabilities
Mathieu Desnoyers267c4022007-10-18 23:41:07 -0700994
Arjan van de Ven97455122008-01-25 21:08:34 +0100995config LATENCYTOP
996 bool "Latency measuring infrastructure"
Randy Dunlap625fdca2010-08-12 12:31:21 -0700997 depends on HAVE_LATENCYTOP_SUPPORT
998 depends on DEBUG_KERNEL
999 depends on STACKTRACE_SUPPORT
1000 depends on PROC_FS
Michal Simek79aac882010-05-25 11:33:26 +02001001 select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE
Arjan van de Ven97455122008-01-25 21:08:34 +01001002 select KALLSYMS
1003 select KALLSYMS_ALL
1004 select STACKTRACE
1005 select SCHEDSTATS
1006 select SCHED_DEBUG
Arjan van de Ven97455122008-01-25 21:08:34 +01001007 help
1008 Enable this option if you want to use the LatencyTOP tool
1009 to find out which userspace is blocking on what kernel operations.
1010
Andi Kleen9e94cd32008-08-16 07:53:05 +02001011config SYSCTL_SYSCALL_CHECK
1012 bool "Sysctl checks"
Eric W. Biederman83ac2012009-04-03 02:22:26 -07001013 depends on SYSCTL
Andi Kleen9e94cd32008-08-16 07:53:05 +02001014 ---help---
1015 sys_sysctl uses binary paths that have been found challenging
1016 to properly maintain and use. This enables checks that help
1017 you to keep things correct.
1018
Akinobu Mita6a11f752009-03-31 15:23:17 -07001019source mm/Kconfig.debug
Arnaldo Carvalho de Melo16444a82008-05-12 21:20:42 +02001020source kernel/trace/Kconfig
1021
Bernhard Kaindlf212ec42008-01-30 13:34:11 +01001022config PROVIDE_OHCI1394_DMA_INIT
Stefan Richter080de8c2008-02-28 20:54:43 +01001023 bool "Remote debugging over FireWire early on boot"
Bernhard Kaindlf212ec42008-01-30 13:34:11 +01001024 depends on PCI && X86
1025 help
1026 If you want to debug problems which hang or crash the kernel early
1027 on boot and the crashing machine has a FireWire port, you can use
1028 this feature to remotely access the memory of the crashed machine
1029 over FireWire. This employs remote DMA as part of the OHCI1394
1030 specification which is now the standard for FireWire controllers.
1031
1032 With remote DMA, you can monitor the printk buffer remotely using
1033 firescope and access all memory below 4GB using fireproxy from gdb.
1034 Even controlling a kernel debugger is possible using remote DMA.
1035
1036 Usage:
1037
1038 If ohci1394_dma=early is used as boot parameter, it will initialize
1039 all OHCI1394 controllers which are found in the PCI config space.
1040
1041 As all changes to the FireWire bus such as enabling and disabling
1042 devices cause a bus reset and thereby disable remote DMA for all
1043 devices, be sure to have the cable plugged and FireWire enabled on
1044 the debugging host before booting the debug target for debugging.
1045
1046 This code (~1k) is freed after boot. By then, the firewire stack
1047 in charge of the OHCI-1394 controllers should be used instead.
1048
1049 See Documentation/debugging-via-ohci1394.txt for more information.
Arjan van de Ven97455122008-01-25 21:08:34 +01001050
Stefan Richter080de8c2008-02-28 20:54:43 +01001051config FIREWIRE_OHCI_REMOTE_DMA
1052 bool "Remote debugging over FireWire with firewire-ohci"
1053 depends on FIREWIRE_OHCI
1054 help
1055 This option lets you use the FireWire bus for remote debugging
1056 with help of the firewire-ohci driver. It enables unfiltered
1057 remote DMA in firewire-ohci.
1058 See Documentation/debugging-via-ohci1394.txt for more information.
1059
1060 If unsure, say N.
1061
Randy Dunlap152de302009-02-20 15:38:47 -08001062config BUILD_DOCSRC
Randy Dunlap3794f3e2008-08-12 15:09:06 -07001063 bool "Build targets in Documentation/ tree"
1064 depends on HEADERS_CHECK
1065 help
1066 This option attempts to build objects from the source files in the
1067 kernel Documentation/ tree.
1068
1069 Say N if you are unsure.
1070
Jason Barone9d376f2009-02-05 11:51:38 -05001071config DYNAMIC_DEBUG
Jason Baron86151fd2009-02-05 11:53:15 -05001072 bool "Enable dynamic printk() support"
Jason Baron346e15b2008-08-12 16:46:19 -04001073 default n
1074 depends on PRINTK
Jason Baron86151fd2009-02-05 11:53:15 -05001075 depends on DEBUG_FS
Jason Baron346e15b2008-08-12 16:46:19 -04001076 help
1077
1078 Compiles debug level messages into the kernel, which would not
1079 otherwise be available at runtime. These messages can then be
Jason Baron86151fd2009-02-05 11:53:15 -05001080 enabled/disabled based on various levels of scope - per source file,
1081 function, module, format string, and line number. This mechanism
1082 implicitly enables all pr_debug() and dev_dbg() calls. The impact of
1083 this compile option is a larger kernel text size of about 2%.
Jason Baron346e15b2008-08-12 16:46:19 -04001084
1085 Usage:
1086
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001087 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
Jason Baron86151fd2009-02-05 11:53:15 -05001088 which is contained in the 'debugfs' filesystem. Thus, the debugfs
1089 filesystem must first be mounted before making use of this feature.
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001090 We refer the control file as: <debugfs>/dynamic_debug/control. This
Jason Baron86151fd2009-02-05 11:53:15 -05001091 file contains a list of the debug statements that can be enabled. The
1092 format for each line of the file is:
Jason Baron346e15b2008-08-12 16:46:19 -04001093
Jason Baron86151fd2009-02-05 11:53:15 -05001094 filename:lineno [module]function flags format
Jason Baron346e15b2008-08-12 16:46:19 -04001095
Jason Baron86151fd2009-02-05 11:53:15 -05001096 filename : source file of the debug statement
1097 lineno : line number of the debug statement
1098 module : module that contains the debug statement
1099 function : function that contains the debug statement
1100 flags : 'p' means the line is turned 'on' for printing
1101 format : the format used for the debug statement
Jason Baron346e15b2008-08-12 16:46:19 -04001102
1103 From a live system:
1104
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001105 nullarbor:~ # cat <debugfs>/dynamic_debug/control
Jason Baron86151fd2009-02-05 11:53:15 -05001106 # filename:lineno [module]function flags format
1107 fs/aio.c:222 [aio]__put_ioctx - "__put_ioctx:\040freeing\040%p\012"
1108 fs/aio.c:248 [aio]ioctx_alloc - "ENOMEM:\040nr_events\040too\040high\012"
1109 fs/aio.c:1770 [aio]sys_io_cancel - "calling\040cancel\012"
Jason Baron346e15b2008-08-12 16:46:19 -04001110
Jason Baron86151fd2009-02-05 11:53:15 -05001111 Example usage:
Jason Baron346e15b2008-08-12 16:46:19 -04001112
Jason Baron86151fd2009-02-05 11:53:15 -05001113 // enable the message at line 1603 of file svcsock.c
1114 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001115 <debugfs>/dynamic_debug/control
Jason Baron346e15b2008-08-12 16:46:19 -04001116
Jason Baron86151fd2009-02-05 11:53:15 -05001117 // enable all the messages in file svcsock.c
1118 nullarbor:~ # echo -n 'file svcsock.c +p' >
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001119 <debugfs>/dynamic_debug/control
Jason Baron346e15b2008-08-12 16:46:19 -04001120
Jason Baron86151fd2009-02-05 11:53:15 -05001121 // enable all the messages in the NFS server module
1122 nullarbor:~ # echo -n 'module nfsd +p' >
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001123 <debugfs>/dynamic_debug/control
Jason Baron346e15b2008-08-12 16:46:19 -04001124
Jason Baron86151fd2009-02-05 11:53:15 -05001125 // enable all 12 messages in the function svc_process()
1126 nullarbor:~ # echo -n 'func svc_process +p' >
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001127 <debugfs>/dynamic_debug/control
Jason Baron346e15b2008-08-12 16:46:19 -04001128
Jason Baron86151fd2009-02-05 11:53:15 -05001129 // disable all 12 messages in the function svc_process()
1130 nullarbor:~ # echo -n 'func svc_process -p' >
Florian Ragwitz2b2f68b2010-05-24 14:33:21 -07001131 <debugfs>/dynamic_debug/control
Jason Baron346e15b2008-08-12 16:46:19 -04001132
Jason Baron86151fd2009-02-05 11:53:15 -05001133 See Documentation/dynamic-debug-howto.txt for additional information.
Jason Baron346e15b2008-08-12 16:46:19 -04001134
Joerg Roedel5ee00bd2009-01-09 12:14:24 +01001135config DMA_API_DEBUG
1136 bool "Enable debugging of DMA-API usage"
1137 depends on HAVE_DMA_API_DEBUG
1138 help
1139 Enable this option to debug the use of the DMA API by device drivers.
1140 With this option you will be able to detect common bugs in device
1141 drivers like double-freeing of DMA mappings or freeing mappings that
1142 were never allocated.
1143 This option causes a performance degredation. Use only if you want
1144 to debug device drivers. If unsure, say N.
Jason Baron346e15b2008-08-12 16:46:19 -04001145
Luca Barbieri86a89382010-02-24 10:54:24 +01001146config ATOMIC64_SELFTEST
1147 bool "Perform an atomic64_t self-test at boot"
1148 help
1149 Enable this option to test the atomic64_t functions at boot.
1150
1151 If unsure, say N.
1152
Mathieu Desnoyers267c4022007-10-18 23:41:07 -07001153source "samples/Kconfig"
Jason Wesseldc7d5522008-04-17 20:05:37 +02001154
1155source "lib/Kconfig.kgdb"
Pekka Enberg0a4af3b2009-02-26 21:38:56 +02001156
1157source "lib/Kconfig.kmemcheck"