Blame view
lib/Kconfig.debug
23.4 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 3 |
config PRINTK_TIME bool "Show timing information on printks" |
d3b8b6e5f [PATCH] kconfig: ... |
4 |
depends on PRINTK |
1da177e4c Linux-2.6.12-rc2 |
5 6 7 8 9 10 |
help Selecting this option causes timing information to be included in printk output. This allows you to measure the interval between kernel operations, including bootup operations. This is useful for identifying long delays in kernel startup. |
de4884439 Permit silencing ... |
11 12 13 14 15 16 17 |
config ENABLE_WARN_DEPRECATED bool "Enable __deprecated logic" default y help Enable the __deprecated logic in the kernel build. Disable this to suppress the "warning: 'foo' is deprecated (declared at kernel/power/somefile.c:1234)" messages. |
cebc04ba9 add CONFIG_ENABLE... |
18 19 20 21 22 23 24 |
config ENABLE_MUST_CHECK bool "Enable __must_check logic" default y help Enable the __must_check logic in the kernel build. Disable this to suppress the "warning: ignoring return value of 'foo', declared with attribute warn_unused_result" messages. |
1da177e4c Linux-2.6.12-rc2 |
25 |
|
35bb5b1e0 Add option to ena... |
26 27 28 29 30 31 32 33 34 35 |
config FRAME_WARN int "Warn for stack frames larger than (needs gcc 4.4)" range 0 8192 default 1024 if !64BIT default 2048 if 64BIT help Tell gcc to warn at build time for stack frames larger than this. Setting this too low will cause a lot of warnings. Setting it to 0 disables the warning. Requires gcc 4.4 |
1da177e4c Linux-2.6.12-rc2 |
36 37 |
config MAGIC_SYSRQ bool "Magic SysRq key" |
f346f4b37 [PATCH] let MAGIC... |
38 |
depends on !UML |
1da177e4c Linux-2.6.12-rc2 |
39 40 41 42 43 44 45 46 47 48 |
help If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you will be able to flush the buffer cache to disk, reboot the system immediately or dump some status information). This is accomplished by pressing various keys while holding SysRq (Alt+PrintScreen). It also works on a serial console (on PC hardware at least), if you send a BREAK and then within 5 seconds a command keypress. The keys are documented in <file:Documentation/sysrq.txt>. Don't say Y unless you really know what this hack does. |
f71d20e96 [PATCH] Add EXPOR... |
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
config UNUSED_SYMBOLS bool "Enable unused/obsolete exported symbols" default y if X86 help Unused but exported symbols make the kernel needlessly bigger. For that reason most of these unused exports will soon be removed. This option is provided temporarily to provide a transition period in case some external kernel module needs one of these symbols anyway. If you encounter such a case in your module, consider if you are actually using the right API. (rationale: since nobody in the kernel is using this in a module, there is a pretty good chance it's actually the wrong interface to use). If you really need the symbol, please send a mail to the linux kernel mailing list mentioning the symbol and why you really need it, and what the merge plan to the mainline kernel for your module is. |
bf4735a46 [PATCH] Kconfig r... |
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 |
config DEBUG_FS bool "Debug Filesystem" depends on SYSFS help debugfs is a virtual file system that kernel developers use to put debugging files into. Enable this option to be able to read and write to these files. If unsure, say N. config HEADERS_CHECK bool "Run 'make headers_check' when building vmlinux" depends on !UML help This option will extract the user-visible kernel headers whenever building the kernel, and will run basic sanity checks on them to ensure that exported files do not attempt to include files which were not exported, etc. If you're making modifications to header files which are relevant for userspace, say 'Y', and check the headers exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in your build tree), to make sure they're suitable. |
91341d4b2 kbuild: introduce... |
87 88 |
config DEBUG_SECTION_MISMATCH bool "Enable full Section mismatch analysis" |
e5f95c8b7 kbuild: print onl... |
89 |
depends on UNDEFINED |
fa2144ba9 kbuild: explain w... |
90 91 92 |
# This option is on purpose disabled for now. # It will be enabled when we are down to a resonable number # of section mismatch warnings (< 10 for an allyesconfig build) |
91341d4b2 kbuild: introduce... |
93 94 95 96 97 98 99 100 |
help The section mismatch analysis checks if there are illegal references from one section to another section. Linux will during link or during runtime drop some sections and any use of code/data previously in these sections will most likely result in an oops. In the code functions and variables are annotated with __init, __devinit etc. (see full list in include/linux/init.h) |
d6fbfa4fc kbuild: Spelling/... |
101 102 103 |
which results in the code/data being placed in specific sections. The section mismatch analysis is always done after a full kernel build but enabling this option will in addition |
91341d4b2 kbuild: introduce... |
104 105 106 |
do the following: - Add the option -fno-inline-functions-called-once to gcc When inlining a function annotated __init in a non-init |
d6fbfa4fc kbuild: Spelling/... |
107 |
function we would lose the section information and thus |
91341d4b2 kbuild: introduce... |
108 |
the analysis would not catch the illegal reference. |
d6fbfa4fc kbuild: Spelling/... |
109 |
This option tells gcc to inline less but will also |
91341d4b2 kbuild: introduce... |
110 111 112 |
result in a larger kernel. - Run the section mismatch analysis for each module/built-in.o When we run the section mismatch analysis on vmlinux.o we |
d6fbfa4fc kbuild: Spelling/... |
113 |
lose valueble information about where the mismatch was |
91341d4b2 kbuild: introduce... |
114 115 116 117 118 |
introduced. Running the analysis for each module/built-in.o file will tell where the mismatch happens much closer to the source. The drawback is that we will report the same mismatch at least twice. |
588ccd732 kbuild: add verbo... |
119 120 |
- Enable verbose reporting from modpost to help solving the section mismatches reported. |
91341d4b2 kbuild: introduce... |
121 |
|
f346f4b37 [PATCH] let MAGIC... |
122 123 124 125 126 |
config DEBUG_KERNEL bool "Kernel debugging" help Say Y here if you are developing drivers or trying to debug and identify kernel problems. |
a304e1b82 [PATCH] Debug sha... |
127 128 129 130 131 132 133 134 |
config DEBUG_SHIRQ bool "Debug shared IRQ handlers" depends on DEBUG_KERNEL && GENERIC_HARDIRQS help Enable this to generate a spurious interrupt as soon as a shared interrupt handler is registered, and just before one is deregistered. Drivers ought to be able to handle interrupts coming in at those points; some don't and need to be caught. |
8446f1d39 [PATCH] detect so... |
135 136 |
config DETECT_SOFTLOCKUP bool "Detect Soft Lockups" |
dea20a3fb [PATCH] Disable D... |
137 |
depends on DEBUG_KERNEL && !S390 |
8446f1d39 [PATCH] detect so... |
138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 |
default y help Say Y here to enable the kernel to detect "soft lockups", which are bugs that cause the kernel to loop in kernel mode for more than 10 seconds, without giving other tasks a chance to run. When a soft-lockup is detected, the kernel will print the current stack trace (which you should report), but the system will stay locked up. This feature has negligible overhead. (Note that "hard lockups" are separate type of bugs that can be detected via the NMI-watchdog, on platforms that support it.) |
b642b6d3f sched: scheduler ... |
153 154 155 156 157 158 159 160 |
config SCHED_DEBUG bool "Collect scheduler debugging info" depends on DEBUG_KERNEL && PROC_FS default y help If you say Y here, the /proc/sched_debug file will be provided that can help debug the scheduler. The runtime overhead of this option is minimal. |
1da177e4c Linux-2.6.12-rc2 |
161 162 163 164 165 166 167 168 169 170 171 |
config SCHEDSTATS bool "Collect scheduler statistics" depends on DEBUG_KERNEL && PROC_FS help If you say Y here, additional code will be inserted into the scheduler and related routines to collect statistics about scheduler behavior and provide them in /proc/schedstat. These stats may be useful for both tuning and debugging the scheduler If you aren't debugging the scheduler or trying to tune a specific application, you can say N to avoid the very slight overhead this adds. |
82f67cd9f [PATCH] Add debug... |
172 173 174 175 176 177 178 179 180 |
config TIMER_STATS bool "Collect kernel timers statistics" depends on DEBUG_KERNEL && PROC_FS help If you say Y here, additional code will be inserted into the timer routines to collect statistics about kernel timers being reprogrammed. The statistics can be read from /proc/timer_stats. The statistics collection is started by writing 1 to /proc/timer_stats, writing 0 stops it. This feature is useful to collect information |
c1a834dc7 timer stats: spee... |
181 182 183 184 |
about timer usage patterns in kernel and userspace. This feature is lightweight if enabled in the kernel config but not activated (it defaults to deactivated on bootup and will only be activated if some application like powertop activates it explicitly). |
82f67cd9f [PATCH] Add debug... |
185 |
|
3ac7fe5a4 infrastructure to... |
186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 |
config DEBUG_OBJECTS bool "Debug object operations" depends on DEBUG_KERNEL help If you say Y here, additional code will be inserted into the kernel to track the life time of various objects and validate the operations on those objects. config DEBUG_OBJECTS_SELFTEST bool "Debug objects selftest" depends on DEBUG_OBJECTS help This enables the selftest of the object debug code. config DEBUG_OBJECTS_FREE bool "Debug objects in freed memory" depends on DEBUG_OBJECTS help This enables checks whether a k/v free operation frees an area which contains an object which has not been deactivated properly. This can make kmalloc/kfree-intensive workloads much slower. |
c6f3a97f8 debugobjects: add... |
208 209 210 211 212 213 214 |
config DEBUG_OBJECTS_TIMERS bool "Debug timer objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the timer routines to track the life time of timer objects and validate the timer operations. |
1da177e4c Linux-2.6.12-rc2 |
215 |
config DEBUG_SLAB |
4a2f0acf0 [PATCH] kconfig: ... |
216 |
bool "Debug slab memory allocations" |
50dd26ba0 [PATCH] DEBUG_SLA... |
217 |
depends on DEBUG_KERNEL && SLAB |
1da177e4c Linux-2.6.12-rc2 |
218 219 220 221 |
help Say Y here to have the kernel do limited verification on memory allocation as well as poisoning memory on free to catch use of freed memory. This can make kmalloc/kfree-intensive workloads much slower. |
871751e25 [PATCH] slab: imp... |
222 223 224 |
config DEBUG_SLAB_LEAK bool "Memory leak debugging" depends on DEBUG_SLAB |
f0630fff5 SLUB: support slu... |
225 226 227 228 229 230 231 232 233 234 235 236 |
config SLUB_DEBUG_ON bool "SLUB debugging on by default" depends on SLUB && SLUB_DEBUG default n help Boot with debugging on by default. SLUB boots by default with the runtime debug capabilities switched off. Enabling this is equivalent to specifying the "slub_debug" parameter on boot. There is no support for more fine grained debug control like possible with slub_debug=xxx. SLUB debugging may be switched off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying "slub_debug=-". |
8ff12cfc0 SLUB: Support for... |
237 238 239 |
config SLUB_STATS default n bool "Enable SLUB performance statistics" |
5b06c853a slub: Deal with c... |
240 |
depends on SLUB && SLUB_DEBUG && SYSFS |
8ff12cfc0 SLUB: Support for... |
241 242 243 244 245 246 247 248 |
help SLUB statistics are useful to debug SLUBs allocation behavior in order find ways to optimize the allocator. This should never be enabled for production use since keeping statistics slows down the allocator by a few percentage points. The slabinfo command supports the determination of the most active slabs to figure out which slabs are relevant to a particular load. Try running: slabinfo -DA |
1da177e4c Linux-2.6.12-rc2 |
249 250 |
config DEBUG_PREEMPT bool "Debug preemptible kernel" |
048c8bc90 [POWERPC] ppc64: ... |
251 |
depends on DEBUG_KERNEL && PREEMPT && (TRACE_IRQFLAGS_SUPPORT || PPC64) |
1da177e4c Linux-2.6.12-rc2 |
252 253 254 255 256 257 |
default y help If you say Y here then the kernel will use a debug variant of the commonly used smp_processor_id() function and will print warnings if kernel code uses it in a preemption-unsafe way. Also, the kernel will detect preemption count underflows. |
e7eebaf6a [PATCH] pi-futex:... |
258 259 |
config DEBUG_RT_MUTEXES bool "RT Mutex debugging, deadlock detection" |
e7eebaf6a [PATCH] pi-futex:... |
260 261 262 263 264 265 266 267 268 |
depends on DEBUG_KERNEL && RT_MUTEXES help This allows rt mutex semantics violations and rt mutex related deadlocks (lockups) to be detected and reported automatically. config DEBUG_PI_LIST bool default y depends on DEBUG_RT_MUTEXES |
61a871228 [PATCH] pi-futex:... |
269 270 |
config RT_MUTEX_TESTER bool "Built-in scriptable tester for rt-mutexes" |
a1583d3e8 [PATCH] fix rt-mu... |
271 |
depends on DEBUG_KERNEL && RT_MUTEXES |
61a871228 [PATCH] pi-futex:... |
272 273 |
help This option enables a rt-mutex tester. |
1da177e4c Linux-2.6.12-rc2 |
274 |
config DEBUG_SPINLOCK |
4d9f34ad3 [PATCH] lockdep: ... |
275 |
bool "Spinlock and rw-lock debugging: basic checks" |
1da177e4c Linux-2.6.12-rc2 |
276 277 278 279 280 281 |
depends on DEBUG_KERNEL help Say Y here and build SMP to catch missing spinlock initialization and certain other kinds of spinlock errors commonly made. This is best used in conjunction with the NMI watchdog so that spinlock deadlocks are also debuggable. |
4d9f34ad3 [PATCH] lockdep: ... |
282 283 284 285 286 287 |
config DEBUG_MUTEXES bool "Mutex debugging: basic checks" depends on DEBUG_KERNEL help This feature allows mutex semantics violations to be detected and reported. |
4d9f34ad3 [PATCH] lockdep: ... |
288 289 |
config DEBUG_LOCK_ALLOC bool "Lock debugging: detect incorrect freeing of live locks" |
517e7aa5b [PATCH] let the t... |
290 |
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
4d9f34ad3 [PATCH] lockdep: ... |
291 292 |
select DEBUG_SPINLOCK select DEBUG_MUTEXES |
4d9f34ad3 [PATCH] lockdep: ... |
293 294 295 296 297 298 299 300 301 302 303 |
select LOCKDEP help This feature will check whether any held lock (spinlock, rwlock, mutex or rwsem) is incorrectly freed by the kernel, via any of the memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), vfree(), etc.), whether a live lock is incorrectly reinitialized via spin_lock_init()/mutex_init()/etc., or whether there is any lock held during task exit. config PROVE_LOCKING bool "Lock debugging: prove locking correctness" |
517e7aa5b [PATCH] let the t... |
304 |
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
4d9f34ad3 [PATCH] lockdep: ... |
305 306 307 |
select LOCKDEP select DEBUG_SPINLOCK select DEBUG_MUTEXES |
4d9f34ad3 [PATCH] lockdep: ... |
308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 |
select DEBUG_LOCK_ALLOC default n help This feature enables the kernel to prove that all locking that occurs in the kernel runtime is mathematically correct: that under no circumstance could an arbitrary (and not yet triggered) combination of observed locking sequences (on an arbitrary number of CPUs, running an arbitrary number of tasks and interrupt contexts) cause a deadlock. In short, this feature enables the kernel to report locking related deadlocks before they actually occur. The proof does not depend on how hard and complex a deadlock scenario would be to trigger: how many participant CPUs, tasks and irq-contexts would be needed for it to trigger. The proof also does not depend on timing: if a race and a resulting deadlock is possible theoretically (no matter how unlikely the race scenario is), it will be proven so and will immediately be reported by the kernel (once the event is observed that makes the deadlock theoretically possible). If a deadlock is impossible (i.e. the locking rules, as observed by the kernel, are mathematically correct), the kernel reports nothing. NOTE: this feature can also be enabled for rwlocks, mutexes and rwsems - in which case all dependencies between these different locking variants are observed and mapped too, and the proof of observed correctness is also maintained for an arbitrary combination of these separate locking variants. For more details, see Documentation/lockdep-design.txt. config LOCKDEP bool |
517e7aa5b [PATCH] let the t... |
346 |
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT |
4d9f34ad3 [PATCH] lockdep: ... |
347 |
select STACKTRACE |
14cf232ab [MIPS] Don't forc... |
348 |
select FRAME_POINTER if !X86 && !MIPS |
4d9f34ad3 [PATCH] lockdep: ... |
349 350 |
select KALLSYMS select KALLSYMS_ALL |
f20786ff4 lockstat: core in... |
351 |
config LOCK_STAT |
fdfb870f8 typo fix Kernel c... |
352 |
bool "Lock usage statistics" |
f20786ff4 lockstat: core in... |
353 354 355 356 357 358 359 360 |
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT select LOCKDEP select DEBUG_SPINLOCK select DEBUG_MUTEXES select DEBUG_LOCK_ALLOC default n help This feature enables tracking lock contention points |
a560aa48e lockstat: documen... |
361 |
For more details, see Documentation/lockstat.txt |
4d9f34ad3 [PATCH] lockdep: ... |
362 363 |
config DEBUG_LOCKDEP bool "Lock dependency engine debugging" |
517e7aa5b [PATCH] let the t... |
364 |
depends on DEBUG_KERNEL && LOCKDEP |
4d9f34ad3 [PATCH] lockdep: ... |
365 366 367 368 369 370 |
help If you say Y here, the lock dependency engine will do additional runtime checks to debug itself, at the price of more runtime overhead. config TRACE_IRQFLAGS |
517e7aa5b [PATCH] let the t... |
371 |
depends on DEBUG_KERNEL |
4d9f34ad3 [PATCH] lockdep: ... |
372 373 374 375 |
bool default y depends on TRACE_IRQFLAGS_SUPPORT depends on PROVE_LOCKING |
1da177e4c Linux-2.6.12-rc2 |
376 |
config DEBUG_SPINLOCK_SLEEP |
4d9f34ad3 [PATCH] lockdep: ... |
377 |
bool "Spinlock debugging: sleep-inside-spinlock checking" |
1da177e4c Linux-2.6.12-rc2 |
378 379 380 381 |
depends on DEBUG_KERNEL help If you say Y here, various routines which may sleep will become very noisy if they are called with a spinlock held. |
cae2ed9aa [PATCH] lockdep: ... |
382 383 384 385 386 387 388 389 390 391 |
config DEBUG_LOCKING_API_SELFTESTS bool "Locking API boot-time self-tests" depends on DEBUG_KERNEL help Say Y here if you want the kernel to run a short self-test during bootup. The self-test checks whether common types of locking bugs are detected by debugging mechanisms or not. (if you disable lock debugging then those bugs wont be detected of course.) The following locking APIs are covered: spinlocks, rwlocks, mutexes and rwsems. |
8637c0990 [PATCH] lockdep: ... |
392 393 |
config STACKTRACE bool |
517e7aa5b [PATCH] let the t... |
394 |
depends on DEBUG_KERNEL |
8637c0990 [PATCH] lockdep: ... |
395 |
depends on STACKTRACE_SUPPORT |
1da177e4c Linux-2.6.12-rc2 |
396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 |
config DEBUG_KOBJECT bool "kobject debugging" depends on DEBUG_KERNEL help If you say Y here, some extra kobject debugging messages will be sent to the syslog. config DEBUG_HIGHMEM bool "Highmem debugging" depends on DEBUG_KERNEL && HIGHMEM help This options enables addition error checking for high memory systems. Disable for production systems. config DEBUG_BUGVERBOSE bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED |
c8538a7aa [PATCH] remove al... |
412 |
depends on BUG |
b920de1b7 mn10300: add the ... |
413 414 |
depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \ FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300 |
1da177e4c Linux-2.6.12-rc2 |
415 416 417 418 419 420 421 422 423 424 425 426 |
default !EMBEDDED help Say Y here to make BUG() panics output the file name and line number of the BUG call as well as the EIP and oops trace. This aids debugging but costs about 70-100K of memory. config DEBUG_INFO bool "Compile the kernel with debug info" depends on DEBUG_KERNEL help If you say Y here the resulting kernel image will include debugging info resulting in a larger kernel image. |
b72e53f8b kconfig.debug: cl... |
427 428 429 |
This adds debug symbols to the kernel and modules (gcc -g), and is needed if you intend to use kernel crashdump or binary object tools like crash, kgdb, LKCD, gdb, etc on the kernel. |
1da177e4c Linux-2.6.12-rc2 |
430 431 432 |
Say Y here only if you plan to debug the kernel. If unsure, say N. |
a241ec65a [PATCH] RCU tortu... |
433 434 435 436 |
config DEBUG_VM bool "Debug VM" depends on DEBUG_KERNEL help |
13e7444b0 [PATCH] mm: remov... |
437 438 |
Enable this to turn on extended checks in the virtual-memory system that may impact performance. |
a241ec65a [PATCH] RCU tortu... |
439 440 |
If unsure, say N. |
ad775f5a8 [PATCH] r/o bind ... |
441 442 443 444 445 446 447 448 449 |
config DEBUG_WRITECOUNT bool "Debug filesystem writers count" depends on DEBUG_KERNEL help Enable this to catch wrong use of the writers count in struct vfsmount. This will increase the size of each file struct by 32 bits. If unsure, say N. |
199a9afc3 [PATCH] Debug var... |
450 451 452 453 454 455 456 457 |
config DEBUG_LIST bool "Debug linked list manipulation" depends on DEBUG_KERNEL help Enable this to turn on extended checks in the linked-list walking routines. If unsure, say N. |
d6ec08420 Add CONFIG_DEBUG_... |
458 459 460 461 462 463 464 465 466 |
config DEBUG_SG bool "Debug SG table operations" depends on DEBUG_KERNEL help Enable this to turn on checks on scatter-gather tables. This can help find problems with drivers that do not properly initialize their sg tables. If unsure, say N. |
1da177e4c Linux-2.6.12-rc2 |
467 468 |
config FRAME_POINTER bool "Compile the kernel with frame pointers" |
b920de1b7 mn10300: add the ... |
469 470 471 |
depends on DEBUG_KERNEL && \ (X86 || CRIS || M68K || M68KNOMMU || FRV || UML || S390 || \ AVR32 || SUPERH || BLACKFIN || MN10300) |
37fce857b [PATCH] uml: spli... |
472 |
default y if DEBUG_INFO && UML |
1da177e4c Linux-2.6.12-rc2 |
473 474 |
help If you say Y here the resulting kernel image will be slightly larger |
2a38bccd0 [PATCH] Kconfig h... |
475 476 |
and slower, but it might give very useful debugging information on some architectures or if you use external debuggers. |
aeb39986e [PATCH] x86-64: A... |
477 |
If you don't debug the kernel, you can say N. |
1da177e4c Linux-2.6.12-rc2 |
478 |
|
bfe8df3d3 slow down printk ... |
479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 |
config BOOT_PRINTK_DELAY bool "Delay each boot printk message by N milliseconds" depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY help This build option allows you to read kernel boot messages by inserting a short delay after each one. The delay is specified in milliseconds on the kernel command line, using "boot_delay=N". It is likely that you would also need to use "lpj=M" to preset the "loops per jiffie" value. See a previous boot log for the "lpj" value to use for your system, and then set "lpj=M" before setting "boot_delay=N". NOTE: Using this option may adversely affect SMP systems. I.e., processors other than the first one may not boot up. BOOT_PRINTK_DELAY also may cause DETECT_SOFTLOCKUP to detect what it believes to be lockup conditions. |
a241ec65a [PATCH] RCU tortu... |
496 497 498 |
config RCU_TORTURE_TEST tristate "torture tests for RCU" depends on DEBUG_KERNEL |
9aaffc898 prohibit rcutortu... |
499 |
depends on m |
a241ec65a [PATCH] RCU tortu... |
500 501 502 503 504 |
default n help This option provides a kernel module that runs torture tests on the RCU infrastructure. The kernel module may be built after the fact on the running kernel to be tested, if desired. |
a241ec65a [PATCH] RCU tortu... |
505 506 |
Say M if you want the RCU torture tests to build as a module. Say N if you are unsure. |
8bb31b9d5 [PATCH] Linux Ker... |
507 |
|
8c1c93564 x86: kprobes: add... |
508 509 510 511 512 513 514 515 516 517 518 |
config KPROBES_SANITY_TEST bool "Kprobes sanity tests" depends on DEBUG_KERNEL depends on KPROBES default n help This option provides for testing basic kprobes functionality on boot. A sample kprobe, jprobe and kretprobe are inserted and verified for functionality. Say N if you are unsure. |
6dab27784 x86: add a simple... |
519 520 521 522 523 524 525 526 527 528 529 |
config BACKTRACE_SELF_TEST tristate "Self test for the backtrace code" depends on DEBUG_KERNEL default n help This option provides a kernel module that can be used to test the kernel stack backtrace code. This option is not useful for distributions or general kernels, but only for kernel developers working on architecture code. Say N if you are unsure. |
8bb31b9d5 [PATCH] Linux Ker... |
530 531 |
config LKDTM tristate "Linux Kernel Dump Test Tool Module" |
bf4735a46 [PATCH] Kconfig r... |
532 |
depends on DEBUG_KERNEL |
8bb31b9d5 [PATCH] Linux Ker... |
533 |
depends on KPROBES |
fddd9cf82 make LKDTM depend... |
534 |
depends on BLOCK |
8bb31b9d5 [PATCH] Linux Ker... |
535 536 537 538 539 540 541 542 543 544 |
default n help This module enables testing of the different dumping mechanisms by inducing system failures at predefined crash points. If you don't need it: say N Choose M here to compile this code as a module. The module will be called lkdtm. Documentation on how to use the module can be found in drivers/misc/lkdtm.c |
6ff1cb355 [PATCH] fault-inj... |
545 546 |
config FAULT_INJECTION |
1ab8509a3 [PATCH] fault-inj... |
547 548 |
bool "Fault-injection framework" depends on DEBUG_KERNEL |
329409aed [PATCH] fault inj... |
549 550 551 |
help Provide fault-injection framework. For more details, see Documentation/fault-injection/. |
6ff1cb355 [PATCH] fault-inj... |
552 |
|
8a8b6502f [PATCH] fault-inj... |
553 |
config FAILSLAB |
1ab8509a3 [PATCH] fault-inj... |
554 555 |
bool "Fault-injection capability for kmalloc" depends on FAULT_INJECTION |
8a8b6502f [PATCH] fault-inj... |
556 |
help |
1ab8509a3 [PATCH] fault-inj... |
557 |
Provide fault-injection capability for kmalloc. |
8a8b6502f [PATCH] fault-inj... |
558 |
|
933e312e7 [PATCH] fault-inj... |
559 560 |
config FAIL_PAGE_ALLOC bool "Fault-injection capabilitiy for alloc_pages()" |
1ab8509a3 [PATCH] fault-inj... |
561 |
depends on FAULT_INJECTION |
933e312e7 [PATCH] fault-inj... |
562 |
help |
1ab8509a3 [PATCH] fault-inj... |
563 |
Provide fault-injection capability for alloc_pages(). |
933e312e7 [PATCH] fault-inj... |
564 |
|
c17bb4951 [PATCH] fault-inj... |
565 |
config FAIL_MAKE_REQUEST |
86327d19f Fix typo in new d... |
566 |
bool "Fault-injection capability for disk IO" |
1ab8509a3 [PATCH] fault-inj... |
567 |
depends on FAULT_INJECTION |
c17bb4951 [PATCH] fault-inj... |
568 |
help |
1ab8509a3 [PATCH] fault-inj... |
569 |
Provide fault-injection capability for disk IO. |
c17bb4951 [PATCH] fault-inj... |
570 |
|
6ff1cb355 [PATCH] fault-inj... |
571 572 |
config FAULT_INJECTION_DEBUG_FS bool "Debugfs entries for fault-injection capabilities" |
1ab8509a3 [PATCH] fault-inj... |
573 |
depends on FAULT_INJECTION && SYSFS && DEBUG_FS |
6ff1cb355 [PATCH] fault-inj... |
574 |
help |
1ab8509a3 [PATCH] fault-inj... |
575 |
Enable configuration of fault-injection capabilities via debugfs. |
1df49008f [PATCH] fault inj... |
576 577 578 579 |
config FAULT_INJECTION_STACKTRACE_FILTER bool "stacktrace filter for fault-injection capabilities" depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT |
6d690dcac fault injection: ... |
580 |
depends on !X86_64 |
1df49008f [PATCH] fault inj... |
581 582 583 584 |
select STACKTRACE select FRAME_POINTER help Provide stacktrace filter for fault-injection capabilities |
267c4025f markers: Add samp... |
585 |
|
9745512ce sched: latencytop... |
586 587 588 589 590 591 592 593 |
config LATENCYTOP bool "Latency measuring infrastructure" select FRAME_POINTER if !MIPS select KALLSYMS select KALLSYMS_ALL select STACKTRACE select SCHEDSTATS select SCHED_DEBUG |
aa7d93506 latencytop: Chang... |
594 |
depends on HAVE_LATENCYTOP_SUPPORT |
9745512ce sched: latencytop... |
595 596 597 |
help Enable this option if you want to use the LatencyTOP tool to find out which userspace is blocking on what kernel operations. |
f212ec4b7 x86: early boot d... |
598 |
config PROVIDE_OHCI1394_DMA_INIT |
080de8c2c firewire: fw-ohci... |
599 |
bool "Remote debugging over FireWire early on boot" |
f212ec4b7 x86: early boot d... |
600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 |
depends on PCI && X86 help If you want to debug problems which hang or crash the kernel early on boot and the crashing machine has a FireWire port, you can use this feature to remotely access the memory of the crashed machine over FireWire. This employs remote DMA as part of the OHCI1394 specification which is now the standard for FireWire controllers. With remote DMA, you can monitor the printk buffer remotely using firescope and access all memory below 4GB using fireproxy from gdb. Even controlling a kernel debugger is possible using remote DMA. Usage: If ohci1394_dma=early is used as boot parameter, it will initialize all OHCI1394 controllers which are found in the PCI config space. As all changes to the FireWire bus such as enabling and disabling devices cause a bus reset and thereby disable remote DMA for all devices, be sure to have the cable plugged and FireWire enabled on the debugging host before booting the debug target for debugging. This code (~1k) is freed after boot. By then, the firewire stack in charge of the OHCI-1394 controllers should be used instead. See Documentation/debugging-via-ohci1394.txt for more information. |
9745512ce sched: latencytop... |
626 |
|
080de8c2c firewire: fw-ohci... |
627 628 629 630 631 632 633 634 635 636 |
config FIREWIRE_OHCI_REMOTE_DMA bool "Remote debugging over FireWire with firewire-ohci" depends on FIREWIRE_OHCI help This option lets you use the FireWire bus for remote debugging with help of the firewire-ohci driver. It enables unfiltered remote DMA in firewire-ohci. See Documentation/debugging-via-ohci1394.txt for more information. If unsure, say N. |
267c4025f markers: Add samp... |
637 |
source "samples/Kconfig" |
dc7d55270 kgdb: core |
638 639 |
source "lib/Kconfig.kgdb" |