Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | |
| 2 | config PRINTK_TIME |
| 3 | bool "Show timing information on printks" |
Randy Dunlap | d3b8b6e | 2006-12-06 20:36:38 -0800 | [diff] [blame] | 4 | depends on PRINTK |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 5 | 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 |
Jim Cromie | 99172a2 | 2011-03-18 11:33:08 -0600 | [diff] [blame] | 10 | in kernel startup. Or add printk.time=1 at boot-time. |
| 11 | See Documentation/kernel-parameters.txt |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 12 | |
Mandeep Singh Baines | 5af5bcb | 2011-03-22 16:34:23 -0700 | [diff] [blame] | 13 | config DEFAULT_MESSAGE_LOGLEVEL |
| 14 | int "Default message log level (1-7)" |
| 15 | range 1 7 |
| 16 | default "4" |
| 17 | help |
| 18 | Default log level for printk statements with no specified priority. |
| 19 | |
| 20 | This was hard-coded to KERN_WARNING since at least 2.6.10 but folks |
| 21 | that are auditing their logs closely may want to set it to a lower |
| 22 | priority. |
| 23 | |
Jeff Garzik | de48844 | 2007-10-25 04:06:13 -0400 | [diff] [blame] | 24 | config ENABLE_WARN_DEPRECATED |
| 25 | bool "Enable __deprecated logic" |
| 26 | default y |
| 27 | help |
| 28 | Enable the __deprecated logic in the kernel build. |
| 29 | Disable this to suppress the "warning: 'foo' is deprecated |
| 30 | (declared at kernel/power/somefile.c:1234)" messages. |
| 31 | |
Andrew Morton | cebc04b | 2006-08-14 22:43:18 -0700 | [diff] [blame] | 32 | config ENABLE_MUST_CHECK |
| 33 | bool "Enable __must_check logic" |
| 34 | default y |
| 35 | help |
| 36 | Enable the __must_check logic in the kernel build. Disable this to |
| 37 | suppress the "warning: ignoring return value of 'foo', declared with |
| 38 | attribute warn_unused_result" messages. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 39 | |
Andi Kleen | 35bb5b1 | 2008-02-22 15:15:03 +0100 | [diff] [blame] | 40 | config FRAME_WARN |
| 41 | int "Warn for stack frames larger than (needs gcc 4.4)" |
| 42 | range 0 8192 |
| 43 | default 1024 if !64BIT |
| 44 | default 2048 if 64BIT |
| 45 | help |
| 46 | Tell gcc to warn at build time for stack frames larger than this. |
| 47 | Setting this too low will cause a lot of warnings. |
| 48 | Setting it to 0 disables the warning. |
| 49 | Requires gcc 4.4 |
| 50 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 51 | config MAGIC_SYSRQ |
| 52 | bool "Magic SysRq key" |
Adrian Bunk | f346f4b | 2006-01-09 20:54:51 -0800 | [diff] [blame] | 53 | depends on !UML |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 54 | help |
| 55 | If you say Y here, you will have some control over the system even |
| 56 | if the system crashes for example during kernel debugging (e.g., you |
| 57 | will be able to flush the buffer cache to disk, reboot the system |
| 58 | immediately or dump some status information). This is accomplished |
| 59 | by pressing various keys while holding SysRq (Alt+PrintScreen). It |
| 60 | also works on a serial console (on PC hardware at least), if you |
| 61 | send a BREAK and then within 5 seconds a command keypress. The |
| 62 | keys are documented in <file:Documentation/sysrq.txt>. Don't say Y |
| 63 | unless you really know what this hack does. |
| 64 | |
Randy Dunlap | 99657c7 | 2009-09-18 12:49:22 -0700 | [diff] [blame] | 65 | config STRIP_ASM_SYMS |
| 66 | bool "Strip assembler-generated symbols during link" |
| 67 | default n |
| 68 | help |
| 69 | Strip internal assembler-generated symbols during a link (symbols |
| 70 | that look like '.Lxxx') so they don't pollute the output of |
| 71 | get_wchan() and suchlike. |
| 72 | |
Arjan van de Ven | f71d20e | 2006-06-28 04:26:45 -0700 | [diff] [blame] | 73 | config UNUSED_SYMBOLS |
| 74 | bool "Enable unused/obsolete exported symbols" |
| 75 | default y if X86 |
| 76 | help |
| 77 | Unused but exported symbols make the kernel needlessly bigger. For |
| 78 | that reason most of these unused exports will soon be removed. This |
| 79 | option is provided temporarily to provide a transition period in case |
| 80 | some external kernel module needs one of these symbols anyway. If you |
| 81 | encounter such a case in your module, consider if you are actually |
| 82 | using the right API. (rationale: since nobody in the kernel is using |
| 83 | this in a module, there is a pretty good chance it's actually the |
| 84 | wrong interface to use). If you really need the symbol, please send a |
| 85 | mail to the linux kernel mailing list mentioning the symbol and why |
| 86 | you really need it, and what the merge plan to the mainline kernel for |
| 87 | your module is. |
| 88 | |
Don Mullis | bf4735a | 2006-12-10 02:18:37 -0800 | [diff] [blame] | 89 | config DEBUG_FS |
| 90 | bool "Debug Filesystem" |
Don Mullis | bf4735a | 2006-12-10 02:18:37 -0800 | [diff] [blame] | 91 | help |
| 92 | debugfs is a virtual file system that kernel developers use to put |
| 93 | debugging files into. Enable this option to be able to read and |
| 94 | write to these files. |
| 95 | |
Robert P. J. Day | ff54333 | 2008-05-20 00:06:00 +0200 | [diff] [blame] | 96 | For detailed documentation on the debugfs API, see |
| 97 | Documentation/DocBook/filesystems. |
| 98 | |
Don Mullis | bf4735a | 2006-12-10 02:18:37 -0800 | [diff] [blame] | 99 | If unsure, say N. |
| 100 | |
| 101 | config HEADERS_CHECK |
| 102 | bool "Run 'make headers_check' when building vmlinux" |
| 103 | depends on !UML |
| 104 | help |
| 105 | This option will extract the user-visible kernel headers whenever |
| 106 | building the kernel, and will run basic sanity checks on them to |
| 107 | ensure that exported files do not attempt to include files which |
| 108 | were not exported, etc. |
| 109 | |
| 110 | If you're making modifications to header files which are |
| 111 | relevant for userspace, say 'Y', and check the headers |
| 112 | exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in |
| 113 | your build tree), to make sure they're suitable. |
| 114 | |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 115 | config DEBUG_SECTION_MISMATCH |
| 116 | bool "Enable full Section mismatch analysis" |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 117 | help |
| 118 | The section mismatch analysis checks if there are illegal |
| 119 | references from one section to another section. |
Michael Witten | e809ab0 | 2011-04-17 04:08:48 +0000 | [diff] [blame] | 120 | During linktime or runtime, some sections are dropped; |
| 121 | any use of code/data previously in these sections would |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 122 | most likely result in an oops. |
Michael Witten | e809ab0 | 2011-04-17 04:08:48 +0000 | [diff] [blame] | 123 | In the code, functions and variables are annotated with |
| 124 | __init, __devinit, etc. (see the full list in include/linux/init.h), |
Geert Uytterhoeven | d6fbfa4 | 2008-01-30 11:13:23 +0100 | [diff] [blame] | 125 | which results in the code/data being placed in specific sections. |
Michael Witten | e809ab0 | 2011-04-17 04:08:48 +0000 | [diff] [blame] | 126 | The section mismatch analysis is always performed after a full |
| 127 | kernel build, and enabling this option causes the following |
| 128 | additional steps to occur: |
| 129 | - Add the option -fno-inline-functions-called-once to gcc commands. |
| 130 | When inlining a function annotated with __init in a non-init |
| 131 | function, we would lose the section information and thus |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 132 | the analysis would not catch the illegal reference. |
Michael Witten | e809ab0 | 2011-04-17 04:08:48 +0000 | [diff] [blame] | 133 | This option tells gcc to inline less (but it does result in |
| 134 | a larger kernel). |
| 135 | - Run the section mismatch analysis for each module/built-in.o file. |
| 136 | When we run the section mismatch analysis on vmlinux.o, we |
Geert Uytterhoeven | d6fbfa4 | 2008-01-30 11:13:23 +0100 | [diff] [blame] | 137 | lose valueble information about where the mismatch was |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 138 | introduced. |
| 139 | Running the analysis for each module/built-in.o file |
Michael Witten | e809ab0 | 2011-04-17 04:08:48 +0000 | [diff] [blame] | 140 | tells where the mismatch happens much closer to the |
| 141 | source. The drawback is that the same mismatch is |
| 142 | reported at least twice. |
| 143 | - Enable verbose reporting from modpost in order to help resolve |
| 144 | the section mismatches that are reported. |
Sam Ravnborg | 91341d4 | 2008-01-21 21:31:44 +0100 | [diff] [blame] | 145 | |
Adrian Bunk | f346f4b | 2006-01-09 20:54:51 -0800 | [diff] [blame] | 146 | config DEBUG_KERNEL |
| 147 | bool "Kernel debugging" |
| 148 | help |
| 149 | Say Y here if you are developing drivers or trying to debug and |
| 150 | identify kernel problems. |
| 151 | |
David Woodhouse | a304e1b | 2007-02-12 00:52:00 -0800 | [diff] [blame] | 152 | config DEBUG_SHIRQ |
| 153 | bool "Debug shared IRQ handlers" |
| 154 | depends on DEBUG_KERNEL && GENERIC_HARDIRQS |
| 155 | help |
| 156 | Enable this to generate a spurious interrupt as soon as a shared |
| 157 | interrupt handler is registered, and just before one is deregistered. |
| 158 | Drivers ought to be able to handle interrupts coming in at those |
| 159 | points; some don't and need to be caught. |
| 160 | |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 161 | config LOCKUP_DETECTOR |
| 162 | bool "Detect Hard and Soft Lockups" |
Heiko Carstens | dea20a3 | 2006-10-11 01:20:44 -0700 | [diff] [blame] | 163 | depends on DEBUG_KERNEL && !S390 |
Ingo Molnar | 8446f1d | 2005-09-06 15:16:27 -0700 | [diff] [blame] | 164 | help |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 165 | Say Y here to enable the kernel to act as a watchdog to detect |
| 166 | hard and soft lockups. |
Don Zickus | 84e478c | 2010-02-05 21:47:05 -0500 | [diff] [blame] | 167 | |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 168 | Softlockups are bugs that cause the kernel to loop in kernel |
Ingo Molnar | 9c44bc0 | 2008-05-12 21:21:04 +0200 | [diff] [blame] | 169 | mode for more than 60 seconds, without giving other tasks a |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 170 | chance to run. The current stack trace is displayed upon |
| 171 | detection and the system will stay locked up. |
Ingo Molnar | 8446f1d | 2005-09-06 15:16:27 -0700 | [diff] [blame] | 172 | |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 173 | Hardlockups are bugs that cause the CPU to loop in kernel mode |
| 174 | for more than 60 seconds, without letting other interrupts have a |
| 175 | chance to run. The current stack trace is displayed upon detection |
| 176 | and the system will stay locked up. |
Ingo Molnar | 8446f1d | 2005-09-06 15:16:27 -0700 | [diff] [blame] | 177 | |
Don Zickus | 58687ac | 2010-05-07 17:11:44 -0400 | [diff] [blame] | 178 | The overhead should be minimal. A periodic hrtimer runs to |
| 179 | generate interrupts and kick the watchdog task every 10-12 seconds. |
| 180 | An NMI is generated every 60 seconds or so to check for hardlockups. |
Don Zickus | 84e478c | 2010-02-05 21:47:05 -0500 | [diff] [blame] | 181 | |
Frederic Weisbecker | 23637d4 | 2010-05-15 23:15:20 +0200 | [diff] [blame] | 182 | config HARDLOCKUP_DETECTOR |
Don Zickus | 4a7863c | 2010-12-22 14:00:03 -0500 | [diff] [blame] | 183 | def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI && \ |
| 184 | !ARCH_HAS_NMI_WATCHDOG |
Ingo Molnar | 8446f1d | 2005-09-06 15:16:27 -0700 | [diff] [blame] | 185 | |
Don Zickus | fef2c9b | 2011-03-22 16:34:16 -0700 | [diff] [blame] | 186 | config BOOTPARAM_HARDLOCKUP_PANIC |
| 187 | bool "Panic (Reboot) On Hard Lockups" |
| 188 | depends on LOCKUP_DETECTOR |
| 189 | help |
| 190 | Say Y here to enable the kernel to panic on "hard lockups", |
| 191 | which are bugs that cause the kernel to loop in kernel |
| 192 | mode with interrupts disabled for more than 60 seconds. |
| 193 | |
| 194 | Say N if unsure. |
| 195 | |
| 196 | config BOOTPARAM_HARDLOCKUP_PANIC_VALUE |
| 197 | int |
| 198 | depends on LOCKUP_DETECTOR |
| 199 | range 0 1 |
| 200 | default 0 if !BOOTPARAM_HARDLOCKUP_PANIC |
| 201 | default 1 if BOOTPARAM_HARDLOCKUP_PANIC |
| 202 | |
Ingo Molnar | 9c44bc0 | 2008-05-12 21:21:04 +0200 | [diff] [blame] | 203 | config BOOTPARAM_SOFTLOCKUP_PANIC |
| 204 | bool "Panic (Reboot) On Soft Lockups" |
Frederic Weisbecker | 89d7ce2 | 2010-05-13 00:27:20 +0200 | [diff] [blame] | 205 | depends on LOCKUP_DETECTOR |
Ingo Molnar | 9c44bc0 | 2008-05-12 21:21:04 +0200 | [diff] [blame] | 206 | help |
| 207 | Say Y here to enable the kernel to panic on "soft lockups", |
| 208 | which are bugs that cause the kernel to loop in kernel |
| 209 | mode for more than 60 seconds, without giving other tasks a |
| 210 | chance to run. |
| 211 | |
| 212 | The panic can be used in combination with panic_timeout, |
| 213 | to cause the system to reboot automatically after a |
| 214 | lockup has been detected. This feature is useful for |
| 215 | high-availability systems that have uptime guarantees and |
| 216 | where a lockup must be resolved ASAP. |
| 217 | |
| 218 | Say N if unsure. |
| 219 | |
| 220 | config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE |
| 221 | int |
Frederic Weisbecker | e16bb1d | 2010-05-15 22:30:22 +0200 | [diff] [blame] | 222 | depends on LOCKUP_DETECTOR |
Ingo Molnar | 9c44bc0 | 2008-05-12 21:21:04 +0200 | [diff] [blame] | 223 | range 0 1 |
| 224 | default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC |
| 225 | default 1 if BOOTPARAM_SOFTLOCKUP_PANIC |
| 226 | |
Mandeep Singh Baines | e162b39 | 2009-01-15 11:08:40 -0800 | [diff] [blame] | 227 | config DETECT_HUNG_TASK |
| 228 | bool "Detect Hung Tasks" |
| 229 | depends on DEBUG_KERNEL |
Anton Blanchard | 8edbb83 | 2011-07-05 13:32:40 +1000 | [diff] [blame] | 230 | default LOCKUP_DETECTOR |
Mandeep Singh Baines | e162b39 | 2009-01-15 11:08:40 -0800 | [diff] [blame] | 231 | help |
| 232 | Say Y here to enable the kernel to detect "hung tasks", |
| 233 | which are bugs that cause the task to be stuck in |
| 234 | uninterruptible "D" state indefinitiley. |
| 235 | |
| 236 | When a hung task is detected, the kernel will print the |
| 237 | current stack trace (which you should report), but the |
| 238 | task will stay in uninterruptible state. If lockdep is |
| 239 | enabled then all held locks will also be reported. This |
| 240 | feature has negligible overhead. |
| 241 | |
Jeff Mahoney | e11feaa | 2011-04-27 14:27:24 -0400 | [diff] [blame] | 242 | config DEFAULT_HUNG_TASK_TIMEOUT |
| 243 | int "Default timeout for hung task detection (in seconds)" |
| 244 | depends on DETECT_HUNG_TASK |
| 245 | default 120 |
| 246 | help |
| 247 | This option controls the default timeout (in seconds) used |
| 248 | to determine when a task has become non-responsive and should |
| 249 | be considered hung. |
| 250 | |
| 251 | It can be adjusted at runtime via the kernel.hung_task_timeout |
| 252 | sysctl or by writing a value to /proc/sys/kernel/hung_task_timeout. |
| 253 | |
| 254 | A timeout of 0 disables the check. The default is two minutes. |
| 255 | Keeping the default should be fine in most cases. |
| 256 | |
Mandeep Singh Baines | e162b39 | 2009-01-15 11:08:40 -0800 | [diff] [blame] | 257 | config BOOTPARAM_HUNG_TASK_PANIC |
| 258 | bool "Panic (Reboot) On Hung Tasks" |
| 259 | depends on DETECT_HUNG_TASK |
| 260 | help |
| 261 | Say Y here to enable the kernel to panic on "hung tasks", |
| 262 | which are bugs that cause the kernel to leave a task stuck |
| 263 | in uninterruptible "D" state. |
| 264 | |
| 265 | The panic can be used in combination with panic_timeout, |
| 266 | to cause the system to reboot automatically after a |
| 267 | hung task has been detected. This feature is useful for |
| 268 | high-availability systems that have uptime guarantees and |
| 269 | where a hung tasks must be resolved ASAP. |
| 270 | |
| 271 | Say N if unsure. |
| 272 | |
| 273 | config BOOTPARAM_HUNG_TASK_PANIC_VALUE |
| 274 | int |
| 275 | depends on DETECT_HUNG_TASK |
| 276 | range 0 1 |
| 277 | default 0 if !BOOTPARAM_HUNG_TASK_PANIC |
| 278 | default 1 if BOOTPARAM_HUNG_TASK_PANIC |
| 279 | |
Ingo Molnar | b642b6d3 | 2007-07-09 18:52:00 +0200 | [diff] [blame] | 280 | config SCHED_DEBUG |
| 281 | bool "Collect scheduler debugging info" |
| 282 | depends on DEBUG_KERNEL && PROC_FS |
| 283 | default y |
| 284 | help |
| 285 | If you say Y here, the /proc/sched_debug file will be provided |
| 286 | that can help debug the scheduler. The runtime overhead of this |
| 287 | option is minimal. |
| 288 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 289 | config SCHEDSTATS |
| 290 | bool "Collect scheduler statistics" |
| 291 | depends on DEBUG_KERNEL && PROC_FS |
| 292 | help |
| 293 | If you say Y here, additional code will be inserted into the |
| 294 | scheduler and related routines to collect statistics about |
| 295 | scheduler behavior and provide them in /proc/schedstat. These |
| 296 | stats may be useful for both tuning and debugging the scheduler |
| 297 | If you aren't debugging the scheduler or trying to tune a specific |
| 298 | application, you can say N to avoid the very slight overhead |
| 299 | this adds. |
| 300 | |
Ingo Molnar | 82f67cd | 2007-02-16 01:28:13 -0800 | [diff] [blame] | 301 | config TIMER_STATS |
| 302 | bool "Collect kernel timers statistics" |
| 303 | depends on DEBUG_KERNEL && PROC_FS |
| 304 | help |
| 305 | If you say Y here, additional code will be inserted into the |
| 306 | timer routines to collect statistics about kernel timers being |
| 307 | reprogrammed. The statistics can be read from /proc/timer_stats. |
| 308 | The statistics collection is started by writing 1 to /proc/timer_stats, |
| 309 | writing 0 stops it. This feature is useful to collect information |
Ingo Molnar | c1a834d | 2007-06-01 00:47:16 -0700 | [diff] [blame] | 310 | about timer usage patterns in kernel and userspace. This feature |
| 311 | is lightweight if enabled in the kernel config but not activated |
| 312 | (it defaults to deactivated on bootup and will only be activated |
| 313 | if some application like powertop activates it explicitly). |
Ingo Molnar | 82f67cd | 2007-02-16 01:28:13 -0800 | [diff] [blame] | 314 | |
Thomas Gleixner | 3ac7fe5 | 2008-04-30 00:55:01 -0700 | [diff] [blame] | 315 | config DEBUG_OBJECTS |
| 316 | bool "Debug object operations" |
| 317 | depends on DEBUG_KERNEL |
| 318 | help |
| 319 | If you say Y here, additional code will be inserted into the |
| 320 | kernel to track the life time of various objects and validate |
| 321 | the operations on those objects. |
| 322 | |
| 323 | config DEBUG_OBJECTS_SELFTEST |
| 324 | bool "Debug objects selftest" |
| 325 | depends on DEBUG_OBJECTS |
| 326 | help |
| 327 | This enables the selftest of the object debug code. |
| 328 | |
| 329 | config DEBUG_OBJECTS_FREE |
| 330 | bool "Debug objects in freed memory" |
| 331 | depends on DEBUG_OBJECTS |
| 332 | help |
| 333 | This enables checks whether a k/v free operation frees an area |
| 334 | which contains an object which has not been deactivated |
| 335 | properly. This can make kmalloc/kfree-intensive workloads |
| 336 | much slower. |
| 337 | |
Thomas Gleixner | c6f3a97 | 2008-04-30 00:55:03 -0700 | [diff] [blame] | 338 | config DEBUG_OBJECTS_TIMERS |
| 339 | bool "Debug timer objects" |
| 340 | depends on DEBUG_OBJECTS |
| 341 | help |
| 342 | If you say Y here, additional code will be inserted into the |
| 343 | timer routines to track the life time of timer objects and |
| 344 | validate the timer operations. |
| 345 | |
Thomas Gleixner | dc186ad | 2009-11-16 01:09:48 +0900 | [diff] [blame] | 346 | config DEBUG_OBJECTS_WORK |
| 347 | bool "Debug work objects" |
| 348 | depends on DEBUG_OBJECTS |
| 349 | help |
| 350 | If you say Y here, additional code will be inserted into the |
| 351 | work queue routines to track the life time of work objects and |
| 352 | validate the work operations. |
| 353 | |
Mathieu Desnoyers | 551d55a | 2010-04-17 08:48:42 -0400 | [diff] [blame] | 354 | config DEBUG_OBJECTS_RCU_HEAD |
| 355 | bool "Debug RCU callbacks objects" |
Mathieu Desnoyers | fc2ecf7 | 2011-02-23 09:42:14 -0800 | [diff] [blame] | 356 | depends on DEBUG_OBJECTS |
Mathieu Desnoyers | 551d55a | 2010-04-17 08:48:42 -0400 | [diff] [blame] | 357 | help |
| 358 | Enable this to turn on debugging of RCU list heads (call_rcu() usage). |
| 359 | |
Tejun Heo | e2852ae | 2010-10-26 14:23:05 -0700 | [diff] [blame] | 360 | config DEBUG_OBJECTS_PERCPU_COUNTER |
| 361 | bool "Debug percpu counter objects" |
| 362 | depends on DEBUG_OBJECTS |
| 363 | help |
| 364 | If you say Y here, additional code will be inserted into the |
| 365 | percpu counter routines to track the life time of percpu counter |
| 366 | objects and validate the percpu counter operations. |
| 367 | |
Ingo Molnar | 3ae7020 | 2008-11-26 10:02:00 +0100 | [diff] [blame] | 368 | config DEBUG_OBJECTS_ENABLE_DEFAULT |
| 369 | int "debug_objects bootup default value (0-1)" |
| 370 | range 0 1 |
| 371 | default "1" |
| 372 | depends on DEBUG_OBJECTS |
| 373 | help |
| 374 | Debug objects boot parameter default value |
| 375 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 376 | config DEBUG_SLAB |
Andrew Morton | 4a2f0ac | 2006-03-25 03:07:22 -0800 | [diff] [blame] | 377 | bool "Debug slab memory allocations" |
Vegard Nossum | 7d46d9e | 2008-04-04 00:51:41 +0200 | [diff] [blame] | 378 | depends on DEBUG_KERNEL && SLAB && !KMEMCHECK |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 379 | help |
| 380 | Say Y here to have the kernel do limited verification on memory |
| 381 | allocation as well as poisoning memory on free to catch use of freed |
| 382 | memory. This can make kmalloc/kfree-intensive workloads much slower. |
| 383 | |
Al Viro | 871751e | 2006-03-25 03:06:39 -0800 | [diff] [blame] | 384 | config DEBUG_SLAB_LEAK |
| 385 | bool "Memory leak debugging" |
| 386 | depends on DEBUG_SLAB |
| 387 | |
Christoph Lameter | f0630ff | 2007-07-15 23:38:14 -0700 | [diff] [blame] | 388 | config SLUB_DEBUG_ON |
| 389 | bool "SLUB debugging on by default" |
Vegard Nossum | 7d46d9e | 2008-04-04 00:51:41 +0200 | [diff] [blame] | 390 | depends on SLUB && SLUB_DEBUG && !KMEMCHECK |
Christoph Lameter | f0630ff | 2007-07-15 23:38:14 -0700 | [diff] [blame] | 391 | default n |
| 392 | help |
| 393 | Boot with debugging on by default. SLUB boots by default with |
| 394 | the runtime debug capabilities switched off. Enabling this is |
| 395 | equivalent to specifying the "slub_debug" parameter on boot. |
| 396 | There is no support for more fine grained debug control like |
| 397 | possible with slub_debug=xxx. SLUB debugging may be switched |
| 398 | off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying |
| 399 | "slub_debug=-". |
| 400 | |
Christoph Lameter | 8ff12cf | 2008-02-07 17:47:41 -0800 | [diff] [blame] | 401 | config SLUB_STATS |
| 402 | default n |
| 403 | bool "Enable SLUB performance statistics" |
Christoph Lameter | ab4d5ed | 2010-10-05 13:57:26 -0500 | [diff] [blame] | 404 | depends on SLUB && SYSFS |
Christoph Lameter | 8ff12cf | 2008-02-07 17:47:41 -0800 | [diff] [blame] | 405 | help |
| 406 | SLUB statistics are useful to debug SLUBs allocation behavior in |
| 407 | order find ways to optimize the allocator. This should never be |
| 408 | enabled for production use since keeping statistics slows down |
| 409 | the allocator by a few percentage points. The slabinfo command |
| 410 | supports the determination of the most active slabs to figure |
| 411 | out which slabs are relevant to a particular load. |
| 412 | Try running: slabinfo -DA |
| 413 | |
Catalin Marinas | 3bba00d | 2009-06-11 13:24:13 +0100 | [diff] [blame] | 414 | config DEBUG_KMEMLEAK |
| 415 | bool "Kernel memory leak detector" |
Heiko Carstens | dfcc3e6 | 2009-10-06 10:33:57 +0200 | [diff] [blame] | 416 | depends on DEBUG_KERNEL && EXPERIMENTAL && !MEMORY_HOTPLUG && \ |
Maxin John | c0a5afb | 2011-03-29 00:15:55 +0300 | [diff] [blame] | 417 | (X86 || ARM || PPC || MIPS || S390 || SPARC64 || SUPERH || MICROBLAZE || TILE) |
Heiko Carstens | dfcc3e6 | 2009-10-06 10:33:57 +0200 | [diff] [blame] | 418 | |
Catalin Marinas | 79e0d9b | 2011-04-27 17:06:19 +0100 | [diff] [blame] | 419 | select DEBUG_FS |
Catalin Marinas | 3bba00d | 2009-06-11 13:24:13 +0100 | [diff] [blame] | 420 | select STACKTRACE if STACKTRACE_SUPPORT |
| 421 | select KALLSYMS |
Randy Dunlap | b60e26a | 2009-11-06 15:33:45 -0800 | [diff] [blame] | 422 | select CRC32 |
Catalin Marinas | 3bba00d | 2009-06-11 13:24:13 +0100 | [diff] [blame] | 423 | help |
| 424 | Say Y here if you want to enable the memory leak |
| 425 | detector. The memory allocation/freeing is traced in a way |
| 426 | similar to the Boehm's conservative garbage collector, the |
| 427 | difference being that the orphan objects are not freed but |
| 428 | only shown in /sys/kernel/debug/kmemleak. Enabling this |
| 429 | feature will introduce an overhead to memory |
| 430 | allocations. See Documentation/kmemleak.txt for more |
| 431 | details. |
| 432 | |
Catalin Marinas | bf96d1e | 2009-06-23 14:40:27 +0100 | [diff] [blame] | 433 | Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances |
| 434 | of finding leaks due to the slab objects poisoning. |
| 435 | |
Catalin Marinas | 3bba00d | 2009-06-11 13:24:13 +0100 | [diff] [blame] | 436 | In order to access the kmemleak file, debugfs needs to be |
| 437 | mounted (usually at /sys/kernel/debug). |
| 438 | |
Catalin Marinas | a9d9058 | 2009-06-25 10:16:11 +0100 | [diff] [blame] | 439 | config DEBUG_KMEMLEAK_EARLY_LOG_SIZE |
| 440 | int "Maximum kmemleak early log entries" |
| 441 | depends on DEBUG_KMEMLEAK |
Heiko Carstens | dfcc3e6 | 2009-10-06 10:33:57 +0200 | [diff] [blame] | 442 | range 200 40000 |
Catalin Marinas | a9d9058 | 2009-06-25 10:16:11 +0100 | [diff] [blame] | 443 | default 400 |
| 444 | help |
| 445 | Kmemleak must track all the memory allocations to avoid |
| 446 | reporting false positives. Since memory may be allocated or |
| 447 | freed before kmemleak is initialised, an early log buffer is |
| 448 | used to store these actions. If kmemleak reports "early log |
| 449 | buffer exceeded", please increase this value. |
| 450 | |
Catalin Marinas | 0822ee4 | 2009-06-11 13:24:14 +0100 | [diff] [blame] | 451 | config DEBUG_KMEMLEAK_TEST |
| 452 | tristate "Simple test for the kernel memory leak detector" |
Daniel Baluta | 9718269 | 2011-04-04 15:06:44 -0700 | [diff] [blame] | 453 | depends on DEBUG_KMEMLEAK && m |
Catalin Marinas | 0822ee4 | 2009-06-11 13:24:14 +0100 | [diff] [blame] | 454 | help |
Daniel Baluta | 9718269 | 2011-04-04 15:06:44 -0700 | [diff] [blame] | 455 | This option enables a module that explicitly leaks memory. |
Catalin Marinas | 0822ee4 | 2009-06-11 13:24:14 +0100 | [diff] [blame] | 456 | |
| 457 | If unsure, say N. |
| 458 | |
Jason Baron | ab0155a | 2010-07-19 11:54:17 +0100 | [diff] [blame] | 459 | config DEBUG_KMEMLEAK_DEFAULT_OFF |
| 460 | bool "Default kmemleak to off" |
| 461 | depends on DEBUG_KMEMLEAK |
| 462 | help |
| 463 | Say Y here to disable kmemleak by default. It can then be enabled |
| 464 | on the command line via kmemleak=on. |
| 465 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 466 | config DEBUG_PREEMPT |
| 467 | bool "Debug preemptible kernel" |
Kumar Gala | 01deab9 | 2009-10-16 07:21:39 +0000 | [diff] [blame] | 468 | depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 469 | default y |
| 470 | help |
| 471 | If you say Y here then the kernel will use a debug variant of the |
| 472 | commonly used smp_processor_id() function and will print warnings |
| 473 | if kernel code uses it in a preemption-unsafe way. Also, the kernel |
| 474 | will detect preemption count underflows. |
| 475 | |
Ingo Molnar | e7eebaf | 2006-06-27 02:54:55 -0700 | [diff] [blame] | 476 | config DEBUG_RT_MUTEXES |
| 477 | bool "RT Mutex debugging, deadlock detection" |
Ingo Molnar | e7eebaf | 2006-06-27 02:54:55 -0700 | [diff] [blame] | 478 | depends on DEBUG_KERNEL && RT_MUTEXES |
| 479 | help |
| 480 | This allows rt mutex semantics violations and rt mutex related |
| 481 | deadlocks (lockups) to be detected and reported automatically. |
| 482 | |
| 483 | config DEBUG_PI_LIST |
| 484 | bool |
| 485 | default y |
| 486 | depends on DEBUG_RT_MUTEXES |
| 487 | |
Thomas Gleixner | 61a8712 | 2006-06-27 02:54:56 -0700 | [diff] [blame] | 488 | config RT_MUTEX_TESTER |
| 489 | bool "Built-in scriptable tester for rt-mutexes" |
Roman Zippel | a1583d3 | 2006-06-27 02:55:00 -0700 | [diff] [blame] | 490 | depends on DEBUG_KERNEL && RT_MUTEXES |
Thomas Gleixner | 61a8712 | 2006-06-27 02:54:56 -0700 | [diff] [blame] | 491 | help |
| 492 | This option enables a rt-mutex tester. |
| 493 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 494 | config DEBUG_SPINLOCK |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 495 | bool "Spinlock and rw-lock debugging: basic checks" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 496 | depends on DEBUG_KERNEL |
| 497 | help |
| 498 | Say Y here and build SMP to catch missing spinlock initialization |
| 499 | and certain other kinds of spinlock errors commonly made. This is |
| 500 | best used in conjunction with the NMI watchdog so that spinlock |
| 501 | deadlocks are also debuggable. |
| 502 | |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 503 | config DEBUG_MUTEXES |
| 504 | bool "Mutex debugging: basic checks" |
| 505 | depends on DEBUG_KERNEL |
| 506 | help |
| 507 | This feature allows mutex semantics violations to be detected and |
| 508 | reported. |
| 509 | |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 510 | config DEBUG_LOCK_ALLOC |
| 511 | bool "Lock debugging: detect incorrect freeing of live locks" |
Adrian Bunk | 517e7aa | 2006-07-14 00:24:32 -0700 | [diff] [blame] | 512 | depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 513 | select DEBUG_SPINLOCK |
| 514 | select DEBUG_MUTEXES |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 515 | select LOCKDEP |
| 516 | help |
| 517 | This feature will check whether any held lock (spinlock, rwlock, |
| 518 | mutex or rwsem) is incorrectly freed by the kernel, via any of the |
| 519 | memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), |
| 520 | vfree(), etc.), whether a live lock is incorrectly reinitialized via |
| 521 | spin_lock_init()/mutex_init()/etc., or whether there is any lock |
| 522 | held during task exit. |
| 523 | |
| 524 | config PROVE_LOCKING |
| 525 | bool "Lock debugging: prove locking correctness" |
Adrian Bunk | 517e7aa | 2006-07-14 00:24:32 -0700 | [diff] [blame] | 526 | depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 527 | select LOCKDEP |
| 528 | select DEBUG_SPINLOCK |
| 529 | select DEBUG_MUTEXES |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 530 | select DEBUG_LOCK_ALLOC |
Steven Rostedt | 46b93b7 | 2010-08-31 16:35:20 -0400 | [diff] [blame] | 531 | select TRACE_IRQFLAGS |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 532 | default n |
| 533 | help |
| 534 | This feature enables the kernel to prove that all locking |
| 535 | that occurs in the kernel runtime is mathematically |
| 536 | correct: that under no circumstance could an arbitrary (and |
| 537 | not yet triggered) combination of observed locking |
| 538 | sequences (on an arbitrary number of CPUs, running an |
| 539 | arbitrary number of tasks and interrupt contexts) cause a |
| 540 | deadlock. |
| 541 | |
| 542 | In short, this feature enables the kernel to report locking |
| 543 | related deadlocks before they actually occur. |
| 544 | |
| 545 | The proof does not depend on how hard and complex a |
| 546 | deadlock scenario would be to trigger: how many |
| 547 | participant CPUs, tasks and irq-contexts would be needed |
| 548 | for it to trigger. The proof also does not depend on |
| 549 | timing: if a race and a resulting deadlock is possible |
| 550 | theoretically (no matter how unlikely the race scenario |
| 551 | is), it will be proven so and will immediately be |
| 552 | reported by the kernel (once the event is observed that |
| 553 | makes the deadlock theoretically possible). |
| 554 | |
| 555 | If a deadlock is impossible (i.e. the locking rules, as |
| 556 | observed by the kernel, are mathematically correct), the |
| 557 | kernel reports nothing. |
| 558 | |
| 559 | NOTE: this feature can also be enabled for rwlocks, mutexes |
| 560 | and rwsems - in which case all dependencies between these |
| 561 | different locking variants are observed and mapped too, and |
| 562 | the proof of observed correctness is also maintained for an |
| 563 | arbitrary combination of these separate locking variants. |
| 564 | |
| 565 | For more details, see Documentation/lockdep-design.txt. |
| 566 | |
Paul E. McKenney | 632ee20 | 2010-02-22 17:04:45 -0800 | [diff] [blame] | 567 | config PROVE_RCU |
| 568 | bool "RCU debugging: prove RCU correctness" |
| 569 | depends on PROVE_LOCKING |
| 570 | default n |
| 571 | help |
| 572 | This feature enables lockdep extensions that check for correct |
| 573 | use of RCU APIs. This is currently under development. Say Y |
| 574 | if you want to debug RCU usage or help work on the PROVE_RCU |
| 575 | feature. |
| 576 | |
| 577 | Say N if you are unsure. |
| 578 | |
Lai Jiangshan | 2b3fc35 | 2010-04-20 16:23:07 +0800 | [diff] [blame] | 579 | config PROVE_RCU_REPEATEDLY |
| 580 | bool "RCU debugging: don't disable PROVE_RCU on first splat" |
| 581 | depends on PROVE_RCU |
| 582 | default n |
| 583 | help |
| 584 | By itself, PROVE_RCU will disable checking upon issuing the |
| 585 | first warning (or "splat"). This feature prevents such |
| 586 | disabling, allowing multiple RCU-lockdep warnings to be printed |
| 587 | on a single reboot. |
| 588 | |
Paul E. McKenney | 2dfbf4d | 2010-09-15 23:30:48 -0700 | [diff] [blame] | 589 | Say Y to allow multiple RCU-lockdep warnings per boot. |
| 590 | |
| 591 | Say N if you are unsure. |
| 592 | |
Paul E. McKenney | ca5ecdd | 2010-04-28 14:39:09 -0700 | [diff] [blame] | 593 | config SPARSE_RCU_POINTER |
| 594 | bool "RCU debugging: sparse-based checks for pointer usage" |
| 595 | default n |
| 596 | help |
| 597 | This feature enables the __rcu sparse annotation for |
| 598 | RCU-protected pointers. This annotation will cause sparse |
| 599 | to flag any non-RCU used of annotated pointers. This can be |
| 600 | helpful when debugging RCU usage. Please note that this feature |
| 601 | is not intended to enforce code cleanliness; it is instead merely |
| 602 | a debugging aid. |
| 603 | |
| 604 | Say Y to make sparse flag questionable use of RCU-protected pointers |
| 605 | |
Lai Jiangshan | 2b3fc35 | 2010-04-20 16:23:07 +0800 | [diff] [blame] | 606 | Say N if you are unsure. |
| 607 | |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 608 | config LOCKDEP |
| 609 | bool |
Adrian Bunk | 517e7aa | 2006-07-14 00:24:32 -0700 | [diff] [blame] | 610 | depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 611 | select STACKTRACE |
Michal Simek | 79aac88 | 2010-05-25 11:33:26 +0200 | [diff] [blame] | 612 | select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 613 | select KALLSYMS |
| 614 | select KALLSYMS_ALL |
| 615 | |
Peter Zijlstra | f20786f | 2007-07-19 01:48:56 -0700 | [diff] [blame] | 616 | config LOCK_STAT |
Danny ter Haar | fdfb870 | 2007-09-24 21:24:43 -0700 | [diff] [blame] | 617 | bool "Lock usage statistics" |
Peter Zijlstra | f20786f | 2007-07-19 01:48:56 -0700 | [diff] [blame] | 618 | depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
| 619 | select LOCKDEP |
| 620 | select DEBUG_SPINLOCK |
| 621 | select DEBUG_MUTEXES |
| 622 | select DEBUG_LOCK_ALLOC |
| 623 | default n |
| 624 | help |
| 625 | This feature enables tracking lock contention points |
| 626 | |
Peter Zijlstra | a560aa4 | 2007-10-07 00:24:33 -0700 | [diff] [blame] | 627 | For more details, see Documentation/lockstat.txt |
| 628 | |
Frederic Weisbecker | dd8b1cf | 2010-02-27 17:10:39 +0100 | [diff] [blame] | 629 | This also enables lock events required by "perf lock", |
| 630 | subcommand of perf. |
| 631 | If you want to use "perf lock", you also need to turn on |
| 632 | CONFIG_EVENT_TRACING. |
Hitoshi Mitake | 84c6f88 | 2010-02-04 16:08:15 +0900 | [diff] [blame] | 633 | |
| 634 | CONFIG_LOCK_STAT defines "contended" and "acquired" lock events. |
Frederic Weisbecker | dd8b1cf | 2010-02-27 17:10:39 +0100 | [diff] [blame] | 635 | (CONFIG_LOCKDEP defines "acquire" and "release" events.) |
Hitoshi Mitake | 84c6f88 | 2010-02-04 16:08:15 +0900 | [diff] [blame] | 636 | |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 637 | config DEBUG_LOCKDEP |
| 638 | bool "Lock dependency engine debugging" |
Adrian Bunk | 517e7aa | 2006-07-14 00:24:32 -0700 | [diff] [blame] | 639 | depends on DEBUG_KERNEL && LOCKDEP |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 640 | help |
| 641 | If you say Y here, the lock dependency engine will do |
| 642 | additional runtime checks to debug itself, at the price |
| 643 | of more runtime overhead. |
| 644 | |
| 645 | config TRACE_IRQFLAGS |
| 646 | bool |
Steven Rostedt | 46b93b7 | 2010-08-31 16:35:20 -0400 | [diff] [blame] | 647 | help |
| 648 | Enables hooks to interrupt enabling and disabling for |
| 649 | either tracing or lock debugging. |
Ingo Molnar | 4d9f34a | 2006-07-03 00:24:55 -0700 | [diff] [blame] | 650 | |
Frederic Weisbecker | d902db1 | 2011-06-08 19:31:56 +0200 | [diff] [blame] | 651 | config DEBUG_ATOMIC_SLEEP |
| 652 | bool "Sleep inside atomic section checking" |
Frederic Weisbecker | e8f7c70 | 2011-06-08 01:51:02 +0200 | [diff] [blame] | 653 | select PREEMPT_COUNT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 654 | depends on DEBUG_KERNEL |
| 655 | help |
| 656 | If you say Y here, various routines which may sleep will become very |
Frederic Weisbecker | d902db1 | 2011-06-08 19:31:56 +0200 | [diff] [blame] | 657 | noisy if they are called inside atomic sections: when a spinlock is |
| 658 | held, inside an rcu read side critical section, inside preempt disabled |
| 659 | sections, inside an interrupt, etc... |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 660 | |
Ingo Molnar | cae2ed9 | 2006-07-03 00:24:48 -0700 | [diff] [blame] | 661 | config DEBUG_LOCKING_API_SELFTESTS |
| 662 | bool "Locking API boot-time self-tests" |
| 663 | depends on DEBUG_KERNEL |
| 664 | help |
| 665 | Say Y here if you want the kernel to run a short self-test during |
| 666 | bootup. The self-test checks whether common types of locking bugs |
| 667 | are detected by debugging mechanisms or not. (if you disable |
| 668 | lock debugging then those bugs wont be detected of course.) |
| 669 | The following locking APIs are covered: spinlocks, rwlocks, |
| 670 | mutexes and rwsems. |
| 671 | |
Ingo Molnar | 8637c09 | 2006-07-03 00:24:38 -0700 | [diff] [blame] | 672 | config STACKTRACE |
| 673 | bool |
| 674 | depends on STACKTRACE_SUPPORT |
| 675 | |
Stephen Boyd | 5ca43f6 | 2011-05-24 17:13:36 -0700 | [diff] [blame] | 676 | config DEBUG_STACK_USAGE |
| 677 | bool "Stack utilization instrumentation" |
| 678 | depends on DEBUG_KERNEL |
| 679 | help |
| 680 | Enables the display of the minimum amount of free stack which each |
| 681 | task has ever had available in the sysrq-T and sysrq-P debug output. |
| 682 | |
| 683 | This option will slow down process creation somewhat. |
| 684 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 685 | config DEBUG_KOBJECT |
| 686 | bool "kobject debugging" |
| 687 | depends on DEBUG_KERNEL |
| 688 | help |
| 689 | If you say Y here, some extra kobject debugging messages will be sent |
| 690 | to the syslog. |
| 691 | |
| 692 | config DEBUG_HIGHMEM |
| 693 | bool "Highmem debugging" |
| 694 | depends on DEBUG_KERNEL && HIGHMEM |
| 695 | help |
| 696 | This options enables addition error checking for high memory systems. |
| 697 | Disable for production systems. |
| 698 | |
| 699 | config DEBUG_BUGVERBOSE |
David Rientjes | 6a108a1 | 2011-01-20 14:44:16 -0800 | [diff] [blame] | 700 | bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT |
Matt Mackall | c8538a7 | 2005-05-01 08:59:01 -0700 | [diff] [blame] | 701 | depends on BUG |
David Howells | b920de1 | 2008-02-08 04:19:31 -0800 | [diff] [blame] | 702 | depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \ |
Chris Metcalf | 3cc39b3 | 2011-06-01 16:06:04 -0400 | [diff] [blame] | 703 | FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300 || TILE |
Alexey Dobriyan | 8420e7e | 2009-12-14 18:00:25 -0800 | [diff] [blame] | 704 | default y |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 705 | help |
| 706 | Say Y here to make BUG() panics output the file name and line number |
| 707 | of the BUG call as well as the EIP and oops trace. This aids |
| 708 | debugging but costs about 70-100K of memory. |
| 709 | |
| 710 | config DEBUG_INFO |
| 711 | bool "Compile the kernel with debug info" |
| 712 | depends on DEBUG_KERNEL |
| 713 | help |
| 714 | If you say Y here the resulting kernel image will include |
| 715 | debugging info resulting in a larger kernel image. |
Andreas Dilger | b72e53f | 2007-03-27 15:21:33 -0600 | [diff] [blame] | 716 | This adds debug symbols to the kernel and modules (gcc -g), and |
| 717 | is needed if you intend to use kernel crashdump or binary object |
| 718 | tools like crash, kgdb, LKCD, gdb, etc on the kernel. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 719 | Say Y here only if you plan to debug the kernel. |
| 720 | |
| 721 | If unsure, say N. |
| 722 | |
Andi Kleen | d6f4ceb | 2010-07-14 15:43:52 +0200 | [diff] [blame] | 723 | config DEBUG_INFO_REDUCED |
| 724 | bool "Reduce debugging information" |
| 725 | depends on DEBUG_INFO |
| 726 | help |
| 727 | If you say Y here gcc is instructed to generate less debugging |
| 728 | information for structure types. This means that tools that |
| 729 | need full debugging information (like kgdb or systemtap) won't |
| 730 | be happy. But if you merely need debugging information to |
| 731 | resolve line numbers there is no loss. Advantage is that |
| 732 | build directory object sizes shrink dramatically over a full |
| 733 | DEBUG_INFO build and compile times are reduced too. |
| 734 | Only works with newer gcc versions. |
| 735 | |
Paul E. McKenney | a241ec6 | 2005-10-30 15:03:12 -0800 | [diff] [blame] | 736 | config DEBUG_VM |
| 737 | bool "Debug VM" |
| 738 | depends on DEBUG_KERNEL |
| 739 | help |
Nick Piggin | 13e7444 | 2006-01-06 00:10:58 -0800 | [diff] [blame] | 740 | Enable this to turn on extended checks in the virtual-memory system |
| 741 | that may impact performance. |
Paul E. McKenney | a241ec6 | 2005-10-30 15:03:12 -0800 | [diff] [blame] | 742 | |
| 743 | If unsure, say N. |
| 744 | |
Jiri Slaby | 59ea746 | 2008-06-12 13:56:40 +0200 | [diff] [blame] | 745 | config DEBUG_VIRTUAL |
| 746 | bool "Debug VM translations" |
| 747 | depends on DEBUG_KERNEL && X86 |
| 748 | help |
| 749 | Enable some costly sanity checks in virtual to page code. This can |
| 750 | catch mistakes with virt_to_page() and friends. |
| 751 | |
| 752 | If unsure, say N. |
| 753 | |
David Howells | 8feae13 | 2009-01-08 12:04:47 +0000 | [diff] [blame] | 754 | config DEBUG_NOMMU_REGIONS |
| 755 | bool "Debug the global anon/private NOMMU mapping region tree" |
| 756 | depends on DEBUG_KERNEL && !MMU |
| 757 | help |
| 758 | This option causes the global tree of anonymous and private mapping |
| 759 | regions to be regularly checked for invalid topology. |
| 760 | |
Dave Hansen | ad775f5 | 2008-02-15 14:38:01 -0800 | [diff] [blame] | 761 | config DEBUG_WRITECOUNT |
| 762 | bool "Debug filesystem writers count" |
| 763 | depends on DEBUG_KERNEL |
| 764 | help |
| 765 | Enable this to catch wrong use of the writers count in struct |
| 766 | vfsmount. This will increase the size of each file struct by |
| 767 | 32 bits. |
| 768 | |
| 769 | If unsure, say N. |
| 770 | |
Mel Gorman | 6b74ab9 | 2008-07-23 21:26:49 -0700 | [diff] [blame] | 771 | config DEBUG_MEMORY_INIT |
David Rientjes | 6a108a1 | 2011-01-20 14:44:16 -0800 | [diff] [blame] | 772 | bool "Debug memory initialisation" if EXPERT |
| 773 | default !EXPERT |
Mel Gorman | 6b74ab9 | 2008-07-23 21:26:49 -0700 | [diff] [blame] | 774 | help |
| 775 | Enable this for additional checks during memory initialisation. |
| 776 | The sanity checks verify aspects of the VM such as the memory model |
| 777 | and other information provided by the architecture. Verbose |
| 778 | information will be printed at KERN_DEBUG loglevel depending |
| 779 | on the mminit_loglevel= command-line option. |
| 780 | |
| 781 | If unsure, say Y |
| 782 | |
Dave Jones | 199a9af | 2006-09-29 01:59:00 -0700 | [diff] [blame] | 783 | config DEBUG_LIST |
| 784 | bool "Debug linked list manipulation" |
| 785 | depends on DEBUG_KERNEL |
| 786 | help |
| 787 | Enable this to turn on extended checks in the linked-list |
| 788 | walking routines. |
| 789 | |
| 790 | If unsure, say N. |
| 791 | |
Artem Bityutskiy | 6d411e6 | 2010-10-26 14:23:05 -0700 | [diff] [blame] | 792 | config TEST_LIST_SORT |
| 793 | bool "Linked list sorting test" |
| 794 | depends on DEBUG_KERNEL |
| 795 | help |
| 796 | Enable this to turn on 'list_sort()' function test. This test is |
| 797 | executed only once during system boot, so affects only boot time. |
| 798 | |
| 799 | If unsure, say N. |
| 800 | |
Jens Axboe | d6ec084 | 2007-10-22 20:01:06 +0200 | [diff] [blame] | 801 | config DEBUG_SG |
| 802 | bool "Debug SG table operations" |
| 803 | depends on DEBUG_KERNEL |
| 804 | help |
| 805 | Enable this to turn on checks on scatter-gather tables. This can |
| 806 | help find problems with drivers that do not properly initialize |
| 807 | their sg tables. |
| 808 | |
| 809 | If unsure, say N. |
| 810 | |
Arjan van de Ven | 1b2439d | 2008-08-15 15:29:38 -0700 | [diff] [blame] | 811 | config DEBUG_NOTIFIERS |
| 812 | bool "Debug notifier call chains" |
| 813 | depends on DEBUG_KERNEL |
| 814 | help |
| 815 | Enable this to turn on sanity checking for notifier call chains. |
| 816 | This is most useful for kernel developers to make sure that |
| 817 | modules properly unregister themselves from notifier chains. |
| 818 | This is a relatively cheap check but if you care about maximum |
| 819 | performance, say N. |
| 820 | |
David Howells | e0e8173 | 2009-09-02 09:13:40 +0100 | [diff] [blame] | 821 | config DEBUG_CREDENTIALS |
| 822 | bool "Debug credential management" |
| 823 | depends on DEBUG_KERNEL |
| 824 | help |
| 825 | Enable this to turn on some debug checking for credential |
| 826 | management. The additional code keeps track of the number of |
| 827 | pointers from task_structs to any given cred struct, and checks to |
| 828 | see that this number never exceeds the usage count of the cred |
| 829 | struct. |
| 830 | |
| 831 | Furthermore, if SELinux is enabled, this also checks that the |
| 832 | security pointer in the cred struct is never seen to be invalid. |
| 833 | |
| 834 | If unsure, say N. |
| 835 | |
Jeff Mahoney | 64dec40 | 2009-01-16 13:23:35 -0500 | [diff] [blame] | 836 | # |
| 837 | # Select this config option from the architecture Kconfig, if it |
Justin P. Mattock | 52288b6 | 2011-08-21 20:02:13 -0700 | [diff] [blame] | 838 | # is preferred to always offer frame pointers as a config |
Jeff Mahoney | 64dec40 | 2009-01-16 13:23:35 -0500 | [diff] [blame] | 839 | # option on the architecture (regardless of KERNEL_DEBUG): |
| 840 | # |
| 841 | config ARCH_WANT_FRAME_POINTERS |
| 842 | bool |
| 843 | help |
| 844 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 845 | config FRAME_POINTER |
| 846 | bool "Compile the kernel with frame pointers" |
David Howells | b920de1 | 2008-02-08 04:19:31 -0800 | [diff] [blame] | 847 | depends on DEBUG_KERNEL && \ |
Geert Uytterhoeven | 7302041 | 2011-01-22 22:35:38 +0100 | [diff] [blame] | 848 | (CRIS || M68K || FRV || UML || \ |
Ingo Molnar | da4276b | 2009-01-07 11:05:10 +0100 | [diff] [blame] | 849 | AVR32 || SUPERH || BLACKFIN || MN10300) || \ |
| 850 | ARCH_WANT_FRAME_POINTERS |
| 851 | default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 852 | help |
Ingo Molnar | da4276b | 2009-01-07 11:05:10 +0100 | [diff] [blame] | 853 | If you say Y here the resulting kernel image will be slightly |
| 854 | larger and slower, but it gives very useful debugging information |
| 855 | in case of kernel bugs. (precise oopses/stacktraces/warnings) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 856 | |
Randy Dunlap | bfe8df3 | 2007-10-16 01:23:46 -0700 | [diff] [blame] | 857 | config BOOT_PRINTK_DELAY |
| 858 | bool "Delay each boot printk message by N milliseconds" |
| 859 | depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY |
| 860 | help |
| 861 | This build option allows you to read kernel boot messages |
| 862 | by inserting a short delay after each one. The delay is |
| 863 | specified in milliseconds on the kernel command line, |
| 864 | using "boot_delay=N". |
| 865 | |
| 866 | It is likely that you would also need to use "lpj=M" to preset |
| 867 | the "loops per jiffie" value. |
| 868 | See a previous boot log for the "lpj" value to use for your |
| 869 | system, and then set "lpj=M" before setting "boot_delay=N". |
| 870 | NOTE: Using this option may adversely affect SMP systems. |
| 871 | I.e., processors other than the first one may not boot up. |
Anton Blanchard | 8edbb83 | 2011-07-05 13:32:40 +1000 | [diff] [blame] | 872 | BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect |
Randy Dunlap | bfe8df3 | 2007-10-16 01:23:46 -0700 | [diff] [blame] | 873 | what it believes to be lockup conditions. |
| 874 | |
Paul E. McKenney | a241ec6 | 2005-10-30 15:03:12 -0800 | [diff] [blame] | 875 | config RCU_TORTURE_TEST |
| 876 | tristate "torture tests for RCU" |
| 877 | depends on DEBUG_KERNEL |
| 878 | default n |
| 879 | help |
| 880 | This option provides a kernel module that runs torture tests |
| 881 | on the RCU infrastructure. The kernel module may be built |
| 882 | after the fact on the running kernel to be tested, if desired. |
| 883 | |
Paul E. McKenney | 31a72bc | 2008-06-18 09:26:49 -0700 | [diff] [blame] | 884 | Say Y here if you want RCU torture tests to be built into |
| 885 | the kernel. |
Paul E. McKenney | a241ec6 | 2005-10-30 15:03:12 -0800 | [diff] [blame] | 886 | Say M if you want the RCU torture tests to build as a module. |
| 887 | Say N if you are unsure. |
Ankita Garg | 8bb31b9 | 2006-10-02 02:17:36 -0700 | [diff] [blame] | 888 | |
Paul E. McKenney | 31a72bc | 2008-06-18 09:26:49 -0700 | [diff] [blame] | 889 | config RCU_TORTURE_TEST_RUNNABLE |
| 890 | bool "torture tests for RCU runnable by default" |
| 891 | depends on RCU_TORTURE_TEST = y |
| 892 | default n |
| 893 | help |
| 894 | This option provides a way to build the RCU torture tests |
| 895 | directly into the kernel without them starting up at boot |
| 896 | time. You can use /proc/sys/kernel/rcutorture_runnable |
| 897 | to manually override this setting. This /proc file is |
| 898 | available only when the RCU torture tests have been built |
| 899 | into the kernel. |
| 900 | |
| 901 | Say Y here if you want the RCU torture tests to start during |
| 902 | boot (you probably don't). |
| 903 | Say N here if you want the RCU torture tests to start only |
| 904 | after being manually enabled via /proc. |
| 905 | |
Paul E. McKenney | b163760 | 2010-06-02 16:21:38 -0700 | [diff] [blame] | 906 | config RCU_CPU_STALL_TIMEOUT |
| 907 | int "RCU CPU stall timeout in seconds" |
Paul E. McKenney | a00e0d71 | 2011-02-08 17:14:39 -0800 | [diff] [blame] | 908 | depends on TREE_RCU || TREE_PREEMPT_RCU |
Paul E. McKenney | b163760 | 2010-06-02 16:21:38 -0700 | [diff] [blame] | 909 | range 3 300 |
| 910 | default 60 |
| 911 | help |
| 912 | If a given RCU grace period extends more than the specified |
| 913 | number of seconds, a CPU stall warning is printed. If the |
| 914 | RCU grace period persists, additional CPU stall warnings are |
| 915 | printed at more widely spaced intervals. |
| 916 | |
Paul E. McKenney | 1ed509a | 2010-02-22 17:05:05 -0800 | [diff] [blame] | 917 | config RCU_CPU_STALL_VERBOSE |
| 918 | bool "Print additional per-task information for RCU_CPU_STALL_DETECTOR" |
Paul E. McKenney | a00e0d71 | 2011-02-08 17:14:39 -0800 | [diff] [blame] | 919 | depends on TREE_PREEMPT_RCU |
Paul E. McKenney | 55ec936 | 2010-04-13 12:22:33 -0700 | [diff] [blame] | 920 | default y |
Paul E. McKenney | 1ed509a | 2010-02-22 17:05:05 -0800 | [diff] [blame] | 921 | help |
| 922 | This option causes RCU to printk detailed per-task information |
| 923 | for any tasks that are stalling the current RCU grace period. |
Paul E. McKenney | 64db4cf | 2008-12-18 21:55:32 +0100 | [diff] [blame] | 924 | |
| 925 | Say N if you are unsure. |
| 926 | |
Paul E. McKenney | 1ed509a | 2010-02-22 17:05:05 -0800 | [diff] [blame] | 927 | Say Y if you want to enable such checks. |
| 928 | |
Ananth N Mavinakayanahalli | 8c1c935 | 2008-01-30 13:32:53 +0100 | [diff] [blame] | 929 | config KPROBES_SANITY_TEST |
| 930 | bool "Kprobes sanity tests" |
| 931 | depends on DEBUG_KERNEL |
| 932 | depends on KPROBES |
| 933 | default n |
| 934 | help |
| 935 | This option provides for testing basic kprobes functionality on |
| 936 | boot. A sample kprobe, jprobe and kretprobe are inserted and |
| 937 | verified for functionality. |
| 938 | |
| 939 | Say N if you are unsure. |
| 940 | |
Arjan van de Ven | 6dab277 | 2008-01-30 13:33:08 +0100 | [diff] [blame] | 941 | config BACKTRACE_SELF_TEST |
| 942 | tristate "Self test for the backtrace code" |
| 943 | depends on DEBUG_KERNEL |
| 944 | default n |
| 945 | help |
| 946 | This option provides a kernel module that can be used to test |
| 947 | the kernel stack backtrace code. This option is not useful |
| 948 | for distributions or general kernels, but only for kernel |
| 949 | developers working on architecture code. |
| 950 | |
Vegard Nossum | ad118c5 | 2008-06-27 18:04:48 +0200 | [diff] [blame] | 951 | Note that if you want to also test saved backtraces, you will |
| 952 | have to enable STACKTRACE as well. |
| 953 | |
Arjan van de Ven | 6dab277 | 2008-01-30 13:33:08 +0100 | [diff] [blame] | 954 | Say N if you are unsure. |
| 955 | |
Tejun Heo | 870d665 | 2008-08-25 19:47:25 +0900 | [diff] [blame] | 956 | config DEBUG_BLOCK_EXT_DEVT |
| 957 | bool "Force extended block device numbers and spread them" |
| 958 | depends on DEBUG_KERNEL |
| 959 | depends on BLOCK |
Jens Axboe | 759f8ca | 2008-08-29 09:06:29 +0200 | [diff] [blame] | 960 | default n |
Tejun Heo | 870d665 | 2008-08-25 19:47:25 +0900 | [diff] [blame] | 961 | help |
Tejun Heo | 0e11e34 | 2008-10-13 10:46:01 +0200 | [diff] [blame] | 962 | BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON |
| 963 | SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT |
| 964 | YOU ARE DOING. Distros, please enable this and fix whatever |
| 965 | is broken. |
| 966 | |
Tejun Heo | 870d665 | 2008-08-25 19:47:25 +0900 | [diff] [blame] | 967 | Conventionally, block device numbers are allocated from |
| 968 | predetermined contiguous area. However, extended block area |
| 969 | may introduce non-contiguous block device numbers. This |
| 970 | option forces most block device numbers to be allocated from |
| 971 | the extended space and spreads them to discover kernel or |
| 972 | userland code paths which assume predetermined contiguous |
| 973 | device number allocation. |
| 974 | |
Tejun Heo | 55dc7db | 2008-09-01 13:44:35 +0200 | [diff] [blame] | 975 | Note that turning on this debug option shuffles all the |
| 976 | device numbers for all IDE and SCSI devices including libata |
| 977 | ones, so root partition specified using device number |
| 978 | directly (via rdev or root=MAJ:MIN) won't work anymore. |
| 979 | Textual device names (root=/dev/sdXn) will continue to work. |
| 980 | |
Tejun Heo | 870d665 | 2008-08-25 19:47:25 +0900 | [diff] [blame] | 981 | Say N if you are unsure. |
| 982 | |
Tejun Heo | 7c756e6 | 2009-06-24 15:13:50 +0900 | [diff] [blame] | 983 | config DEBUG_FORCE_WEAK_PER_CPU |
| 984 | bool "Force weak per-cpu definitions" |
| 985 | depends on DEBUG_KERNEL |
| 986 | help |
| 987 | s390 and alpha require percpu variables in modules to be |
| 988 | defined weak to work around addressing range issue which |
| 989 | puts the following two restrictions on percpu variable |
| 990 | definitions. |
| 991 | |
| 992 | 1. percpu symbols must be unique whether static or not |
| 993 | 2. percpu variables can't be defined inside a function |
| 994 | |
| 995 | To ensure that generic code follows the above rules, this |
| 996 | option forces all percpu variables to be defined as weak. |
| 997 | |
Stephen Boyd | 44ec7ab | 2011-05-24 17:13:32 -0700 | [diff] [blame] | 998 | config DEBUG_PER_CPU_MAPS |
| 999 | bool "Debug access to per_cpu maps" |
| 1000 | depends on DEBUG_KERNEL |
| 1001 | depends on SMP |
| 1002 | help |
| 1003 | Say Y to verify that the per_cpu map being accessed has |
| 1004 | been set up. This adds a fair amount of code to kernel memory |
| 1005 | and decreases performance. |
| 1006 | |
| 1007 | Say N if unsure. |
| 1008 | |
Ankita Garg | 8bb31b9 | 2006-10-02 02:17:36 -0700 | [diff] [blame] | 1009 | config LKDTM |
| 1010 | tristate "Linux Kernel Dump Test Tool Module" |
Simon Kagstrom | 0347af4 | 2010-03-05 13:42:49 -0800 | [diff] [blame] | 1011 | depends on DEBUG_FS |
Chris Snook | fddd9cf | 2008-02-23 15:23:26 -0800 | [diff] [blame] | 1012 | depends on BLOCK |
Ankita Garg | 8bb31b9 | 2006-10-02 02:17:36 -0700 | [diff] [blame] | 1013 | default n |
| 1014 | help |
| 1015 | This module enables testing of the different dumping mechanisms by |
| 1016 | inducing system failures at predefined crash points. |
| 1017 | If you don't need it: say N |
| 1018 | Choose M here to compile this code as a module. The module will be |
| 1019 | called lkdtm. |
| 1020 | |
| 1021 | Documentation on how to use the module can be found in |
Simon Kagstrom | 0347af4 | 2010-03-05 13:42:49 -0800 | [diff] [blame] | 1022 | Documentation/fault-injection/provoke-crashes.txt |
Akinobu Mita | 6ff1cb3 | 2006-12-08 02:39:43 -0800 | [diff] [blame] | 1023 | |
Akinobu Mita | c9d221f | 2010-05-26 14:43:36 -0700 | [diff] [blame] | 1024 | config CPU_NOTIFIER_ERROR_INJECT |
| 1025 | tristate "CPU notifier error injection module" |
| 1026 | depends on HOTPLUG_CPU && DEBUG_KERNEL |
| 1027 | help |
| 1028 | This option provides a kernel module that can be used to test |
| 1029 | the error handling of the cpu notifiers |
| 1030 | |
| 1031 | To compile this code as a module, choose M here: the module will |
| 1032 | be called cpu-notifier-error-inject. |
| 1033 | |
| 1034 | If unsure, say N. |
| 1035 | |
Akinobu Mita | 6ff1cb3 | 2006-12-08 02:39:43 -0800 | [diff] [blame] | 1036 | config FAULT_INJECTION |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1037 | bool "Fault-injection framework" |
| 1038 | depends on DEBUG_KERNEL |
Akinobu Mita | 329409a | 2006-12-08 02:39:48 -0800 | [diff] [blame] | 1039 | help |
| 1040 | Provide fault-injection framework. |
| 1041 | For more details, see Documentation/fault-injection/. |
Akinobu Mita | 6ff1cb3 | 2006-12-08 02:39:43 -0800 | [diff] [blame] | 1042 | |
Akinobu Mita | 8a8b650 | 2006-12-08 02:39:44 -0800 | [diff] [blame] | 1043 | config FAILSLAB |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1044 | bool "Fault-injection capability for kmalloc" |
| 1045 | depends on FAULT_INJECTION |
Akinobu Mita | 773ff60 | 2008-12-23 19:37:01 +0900 | [diff] [blame] | 1046 | depends on SLAB || SLUB |
Akinobu Mita | 8a8b650 | 2006-12-08 02:39:44 -0800 | [diff] [blame] | 1047 | help |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1048 | Provide fault-injection capability for kmalloc. |
Akinobu Mita | 8a8b650 | 2006-12-08 02:39:44 -0800 | [diff] [blame] | 1049 | |
Akinobu Mita | 933e312 | 2006-12-08 02:39:45 -0800 | [diff] [blame] | 1050 | config FAIL_PAGE_ALLOC |
| 1051 | bool "Fault-injection capabilitiy for alloc_pages()" |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1052 | depends on FAULT_INJECTION |
Akinobu Mita | 933e312 | 2006-12-08 02:39:45 -0800 | [diff] [blame] | 1053 | help |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1054 | Provide fault-injection capability for alloc_pages(). |
Akinobu Mita | 933e312 | 2006-12-08 02:39:45 -0800 | [diff] [blame] | 1055 | |
Akinobu Mita | c17bb49 | 2006-12-08 02:39:46 -0800 | [diff] [blame] | 1056 | config FAIL_MAKE_REQUEST |
Dave Jones | 86327d1 | 2006-12-12 20:16:36 +0100 | [diff] [blame] | 1057 | bool "Fault-injection capability for disk IO" |
Jens Axboe | 581d4e2 | 2008-09-14 05:56:33 -0700 | [diff] [blame] | 1058 | depends on FAULT_INJECTION && BLOCK |
Akinobu Mita | c17bb49 | 2006-12-08 02:39:46 -0800 | [diff] [blame] | 1059 | help |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1060 | Provide fault-injection capability for disk IO. |
Akinobu Mita | c17bb49 | 2006-12-08 02:39:46 -0800 | [diff] [blame] | 1061 | |
Jens Axboe | 581d4e2 | 2008-09-14 05:56:33 -0700 | [diff] [blame] | 1062 | config FAIL_IO_TIMEOUT |
Takuya Yoshikawa | f4d0143 | 2010-07-21 16:05:53 +0900 | [diff] [blame] | 1063 | bool "Fault-injection capability for faking disk interrupts" |
Jens Axboe | 581d4e2 | 2008-09-14 05:56:33 -0700 | [diff] [blame] | 1064 | depends on FAULT_INJECTION && BLOCK |
| 1065 | help |
| 1066 | Provide fault-injection capability on end IO handling. This |
| 1067 | will make the block layer "forget" an interrupt as configured, |
| 1068 | thus exercising the error handling. |
| 1069 | |
| 1070 | Only works with drivers that use the generic timeout handling, |
| 1071 | for others it wont do anything. |
| 1072 | |
Akinobu Mita | 6ff1cb3 | 2006-12-08 02:39:43 -0800 | [diff] [blame] | 1073 | config FAULT_INJECTION_DEBUG_FS |
| 1074 | bool "Debugfs entries for fault-injection capabilities" |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1075 | depends on FAULT_INJECTION && SYSFS && DEBUG_FS |
Akinobu Mita | 6ff1cb3 | 2006-12-08 02:39:43 -0800 | [diff] [blame] | 1076 | help |
Andrew Morton | 1ab8509a | 2006-12-08 02:39:49 -0800 | [diff] [blame] | 1077 | Enable configuration of fault-injection capabilities via debugfs. |
Akinobu Mita | 1df4900 | 2007-02-20 13:57:56 -0800 | [diff] [blame] | 1078 | |
| 1079 | config FAULT_INJECTION_STACKTRACE_FILTER |
| 1080 | bool "stacktrace filter for fault-injection capabilities" |
| 1081 | depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT |
Akinobu Mita | 6d690dc | 2007-05-12 10:36:53 -0700 | [diff] [blame] | 1082 | depends on !X86_64 |
Akinobu Mita | 1df4900 | 2007-02-20 13:57:56 -0800 | [diff] [blame] | 1083 | select STACKTRACE |
Michal Simek | 79aac88 | 2010-05-25 11:33:26 +0200 | [diff] [blame] | 1084 | select FRAME_POINTER if !PPC && !S390 && !MICROBLAZE |
Akinobu Mita | 1df4900 | 2007-02-20 13:57:56 -0800 | [diff] [blame] | 1085 | help |
| 1086 | Provide stacktrace filter for fault-injection capabilities |
Mathieu Desnoyers | 267c402 | 2007-10-18 23:41:07 -0700 | [diff] [blame] | 1087 | |
Arjan van de Ven | 9745512 | 2008-01-25 21:08:34 +0100 | [diff] [blame] | 1088 | config LATENCYTOP |
| 1089 | bool "Latency measuring infrastructure" |
Randy Dunlap | 625fdca | 2010-08-12 12:31:21 -0700 | [diff] [blame] | 1090 | depends on HAVE_LATENCYTOP_SUPPORT |
| 1091 | depends on DEBUG_KERNEL |
| 1092 | depends on STACKTRACE_SUPPORT |
| 1093 | depends on PROC_FS |
Michal Simek | 79aac88 | 2010-05-25 11:33:26 +0200 | [diff] [blame] | 1094 | select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE |
Arjan van de Ven | 9745512 | 2008-01-25 21:08:34 +0100 | [diff] [blame] | 1095 | select KALLSYMS |
| 1096 | select KALLSYMS_ALL |
| 1097 | select STACKTRACE |
| 1098 | select SCHEDSTATS |
| 1099 | select SCHED_DEBUG |
Arjan van de Ven | 9745512 | 2008-01-25 21:08:34 +0100 | [diff] [blame] | 1100 | help |
| 1101 | Enable this option if you want to use the LatencyTOP tool |
| 1102 | to find out which userspace is blocking on what kernel operations. |
| 1103 | |
Andi Kleen | 9e94cd3 | 2008-08-16 07:53:05 +0200 | [diff] [blame] | 1104 | config SYSCTL_SYSCALL_CHECK |
| 1105 | bool "Sysctl checks" |
Eric W. Biederman | 83ac201 | 2009-04-03 02:22:26 -0700 | [diff] [blame] | 1106 | depends on SYSCTL |
Andi Kleen | 9e94cd3 | 2008-08-16 07:53:05 +0200 | [diff] [blame] | 1107 | ---help--- |
| 1108 | sys_sysctl uses binary paths that have been found challenging |
| 1109 | to properly maintain and use. This enables checks that help |
| 1110 | you to keep things correct. |
| 1111 | |
Akinobu Mita | 6a11f75 | 2009-03-31 15:23:17 -0700 | [diff] [blame] | 1112 | source mm/Kconfig.debug |
Arnaldo Carvalho de Melo | 16444a8 | 2008-05-12 21:20:42 +0200 | [diff] [blame] | 1113 | source kernel/trace/Kconfig |
| 1114 | |
Bernhard Kaindl | f212ec4 | 2008-01-30 13:34:11 +0100 | [diff] [blame] | 1115 | config PROVIDE_OHCI1394_DMA_INIT |
Stefan Richter | 080de8c | 2008-02-28 20:54:43 +0100 | [diff] [blame] | 1116 | bool "Remote debugging over FireWire early on boot" |
Bernhard Kaindl | f212ec4 | 2008-01-30 13:34:11 +0100 | [diff] [blame] | 1117 | depends on PCI && X86 |
| 1118 | help |
| 1119 | If you want to debug problems which hang or crash the kernel early |
| 1120 | on boot and the crashing machine has a FireWire port, you can use |
| 1121 | this feature to remotely access the memory of the crashed machine |
| 1122 | over FireWire. This employs remote DMA as part of the OHCI1394 |
| 1123 | specification which is now the standard for FireWire controllers. |
| 1124 | |
| 1125 | With remote DMA, you can monitor the printk buffer remotely using |
| 1126 | firescope and access all memory below 4GB using fireproxy from gdb. |
| 1127 | Even controlling a kernel debugger is possible using remote DMA. |
| 1128 | |
| 1129 | Usage: |
| 1130 | |
| 1131 | If ohci1394_dma=early is used as boot parameter, it will initialize |
| 1132 | all OHCI1394 controllers which are found in the PCI config space. |
| 1133 | |
| 1134 | As all changes to the FireWire bus such as enabling and disabling |
| 1135 | devices cause a bus reset and thereby disable remote DMA for all |
| 1136 | devices, be sure to have the cable plugged and FireWire enabled on |
| 1137 | the debugging host before booting the debug target for debugging. |
| 1138 | |
| 1139 | This code (~1k) is freed after boot. By then, the firewire stack |
| 1140 | in charge of the OHCI-1394 controllers should be used instead. |
| 1141 | |
| 1142 | See Documentation/debugging-via-ohci1394.txt for more information. |
Arjan van de Ven | 9745512 | 2008-01-25 21:08:34 +0100 | [diff] [blame] | 1143 | |
Stefan Richter | 080de8c | 2008-02-28 20:54:43 +0100 | [diff] [blame] | 1144 | config FIREWIRE_OHCI_REMOTE_DMA |
| 1145 | bool "Remote debugging over FireWire with firewire-ohci" |
| 1146 | depends on FIREWIRE_OHCI |
| 1147 | help |
| 1148 | This option lets you use the FireWire bus for remote debugging |
| 1149 | with help of the firewire-ohci driver. It enables unfiltered |
| 1150 | remote DMA in firewire-ohci. |
| 1151 | See Documentation/debugging-via-ohci1394.txt for more information. |
| 1152 | |
| 1153 | If unsure, say N. |
| 1154 | |
Randy Dunlap | 152de30 | 2009-02-20 15:38:47 -0800 | [diff] [blame] | 1155 | config BUILD_DOCSRC |
Randy Dunlap | 3794f3e | 2008-08-12 15:09:06 -0700 | [diff] [blame] | 1156 | bool "Build targets in Documentation/ tree" |
| 1157 | depends on HEADERS_CHECK |
| 1158 | help |
| 1159 | This option attempts to build objects from the source files in the |
| 1160 | kernel Documentation/ tree. |
| 1161 | |
| 1162 | Say N if you are unsure. |
| 1163 | |
Jason Baron | e9d376f | 2009-02-05 11:51:38 -0500 | [diff] [blame] | 1164 | config DYNAMIC_DEBUG |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1165 | bool "Enable dynamic printk() support" |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1166 | default n |
| 1167 | depends on PRINTK |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1168 | depends on DEBUG_FS |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1169 | help |
| 1170 | |
| 1171 | Compiles debug level messages into the kernel, which would not |
| 1172 | otherwise be available at runtime. These messages can then be |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1173 | enabled/disabled based on various levels of scope - per source file, |
| 1174 | function, module, format string, and line number. This mechanism |
| 1175 | implicitly enables all pr_debug() and dev_dbg() calls. The impact of |
| 1176 | this compile option is a larger kernel text size of about 2%. |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1177 | |
| 1178 | Usage: |
| 1179 | |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1180 | Dynamic debugging is controlled via the 'dynamic_debug/control' file, |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1181 | which is contained in the 'debugfs' filesystem. Thus, the debugfs |
| 1182 | filesystem must first be mounted before making use of this feature. |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1183 | We refer the control file as: <debugfs>/dynamic_debug/control. This |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1184 | file contains a list of the debug statements that can be enabled. The |
| 1185 | format for each line of the file is: |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1186 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1187 | filename:lineno [module]function flags format |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1188 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1189 | filename : source file of the debug statement |
| 1190 | lineno : line number of the debug statement |
| 1191 | module : module that contains the debug statement |
| 1192 | function : function that contains the debug statement |
| 1193 | flags : 'p' means the line is turned 'on' for printing |
| 1194 | format : the format used for the debug statement |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1195 | |
| 1196 | From a live system: |
| 1197 | |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1198 | nullarbor:~ # cat <debugfs>/dynamic_debug/control |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1199 | # filename:lineno [module]function flags format |
| 1200 | fs/aio.c:222 [aio]__put_ioctx - "__put_ioctx:\040freeing\040%p\012" |
| 1201 | fs/aio.c:248 [aio]ioctx_alloc - "ENOMEM:\040nr_events\040too\040high\012" |
| 1202 | fs/aio.c:1770 [aio]sys_io_cancel - "calling\040cancel\012" |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1203 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1204 | Example usage: |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1205 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1206 | // enable the message at line 1603 of file svcsock.c |
| 1207 | nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' > |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1208 | <debugfs>/dynamic_debug/control |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1209 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1210 | // enable all the messages in file svcsock.c |
| 1211 | nullarbor:~ # echo -n 'file svcsock.c +p' > |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1212 | <debugfs>/dynamic_debug/control |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1213 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1214 | // enable all the messages in the NFS server module |
| 1215 | nullarbor:~ # echo -n 'module nfsd +p' > |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1216 | <debugfs>/dynamic_debug/control |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1217 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1218 | // enable all 12 messages in the function svc_process() |
| 1219 | nullarbor:~ # echo -n 'func svc_process +p' > |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1220 | <debugfs>/dynamic_debug/control |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1221 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1222 | // disable all 12 messages in the function svc_process() |
| 1223 | nullarbor:~ # echo -n 'func svc_process -p' > |
Florian Ragwitz | 2b2f68b | 2010-05-24 14:33:21 -0700 | [diff] [blame] | 1224 | <debugfs>/dynamic_debug/control |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1225 | |
Jason Baron | 86151fd | 2009-02-05 11:53:15 -0500 | [diff] [blame] | 1226 | See Documentation/dynamic-debug-howto.txt for additional information. |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1227 | |
Joerg Roedel | 5ee00bd | 2009-01-09 12:14:24 +0100 | [diff] [blame] | 1228 | config DMA_API_DEBUG |
| 1229 | bool "Enable debugging of DMA-API usage" |
| 1230 | depends on HAVE_DMA_API_DEBUG |
| 1231 | help |
| 1232 | Enable this option to debug the use of the DMA API by device drivers. |
| 1233 | With this option you will be able to detect common bugs in device |
| 1234 | drivers like double-freeing of DMA mappings or freeing mappings that |
| 1235 | were never allocated. |
| 1236 | This option causes a performance degredation. Use only if you want |
| 1237 | to debug device drivers. If unsure, say N. |
Jason Baron | 346e15b | 2008-08-12 16:46:19 -0400 | [diff] [blame] | 1238 | |
Luca Barbieri | 86a8938 | 2010-02-24 10:54:24 +0100 | [diff] [blame] | 1239 | config ATOMIC64_SELFTEST |
| 1240 | bool "Perform an atomic64_t self-test at boot" |
| 1241 | help |
| 1242 | Enable this option to test the atomic64_t functions at boot. |
| 1243 | |
| 1244 | If unsure, say N. |
| 1245 | |
Dan Williams | 400fb7f | 2010-10-07 15:25:04 -0700 | [diff] [blame] | 1246 | config ASYNC_RAID6_TEST |
| 1247 | tristate "Self test for hardware accelerated raid6 recovery" |
| 1248 | depends on ASYNC_RAID6_RECOV |
| 1249 | select ASYNC_MEMCPY |
| 1250 | ---help--- |
| 1251 | This is a one-shot self test that permutes through the |
| 1252 | recovery of all the possible two disk failure scenarios for a |
| 1253 | N-disk array. Recovery is performed with the asynchronous |
| 1254 | raid6 recovery routines, and will optionally use an offload |
| 1255 | engine if one is available. |
| 1256 | |
| 1257 | If unsure, say N. |
| 1258 | |
Mathieu Desnoyers | 267c402 | 2007-10-18 23:41:07 -0700 | [diff] [blame] | 1259 | source "samples/Kconfig" |
Jason Wessel | dc7d552 | 2008-04-17 20:05:37 +0200 | [diff] [blame] | 1260 | |
| 1261 | source "lib/Kconfig.kgdb" |
Pekka Enberg | 0a4af3b | 2009-02-26 21:38:56 +0200 | [diff] [blame] | 1262 | |
| 1263 | source "lib/Kconfig.kmemcheck" |
Alexey Dobriyan | 33ee3b2 | 2011-03-22 16:34:40 -0700 | [diff] [blame] | 1264 | |
| 1265 | config TEST_KSTRTOX |
| 1266 | tristate "Test kstrto*() family of functions at runtime" |