Kconfig.debug 49.9 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3

config PRINTK_TIME
	bool "Show timing information on printks"
4
	depends on PRINTK
L
Linus Torvalds 已提交
5
	help
6 7 8 9 10 11 12 13 14 15
	  Selecting this option causes time stamps of the printk()
	  messages to be added to the output of the syslog() system
	  call and at the console.

	  The timestamp is always recorded internally, and exported
	  to /dev/kmsg. This flag just specifies if the timestamp should
	  be included, not that the timestamp is recorded.

	  The behavior is also controlled by the kernel command line
	  parameter printk.time=1. See Documentation/kernel-parameters.txt
L
Linus Torvalds 已提交
16

17 18 19 20 21 22 23 24 25 26 27
config DEFAULT_MESSAGE_LOGLEVEL
	int "Default message log level (1-7)"
	range 1 7
	default "4"
	help
	  Default log level for printk statements with no specified priority.

	  This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
	  that are auditing their logs closely may want to set it to a lower
	  priority.

28 29 30 31 32 33 34 35
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.

A
Andrew Morton 已提交
36 37 38 39 40 41 42
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.
L
Linus Torvalds 已提交
43

44 45 46 47 48 49 50 51 52 53 54
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

L
Linus Torvalds 已提交
55 56
config MAGIC_SYSRQ
	bool "Magic SysRq key"
57
	depends on !UML
L
Linus Torvalds 已提交
58 59 60 61 62 63 64 65 66 67 68
	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.

69 70 71 72 73 74 75 76
config STRIP_ASM_SYMS
	bool "Strip assembler-generated symbols during link"
	default n
	help
	  Strip internal assembler-generated symbols during a link (symbols
	  that look like '.Lxxx') so they don't pollute the output of
	  get_wchan() and suchlike.

A
Andi Kleen 已提交
77 78 79 80 81 82 83 84 85
config READABLE_ASM
        bool "Generate readable assembler code"
        depends on DEBUG_KERNEL
        help
          Disable some compiler optimizations that tend to generate human unreadable
          assembler output. This may make the kernel slightly slower, but it helps
          to keep kernel developers who have to stare a lot at assembler listings
          sane.

86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101
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.

102 103 104 105 106 107 108
config DEBUG_FS
	bool "Debug Filesystem"
	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.

109 110 111
	  For detailed documentation on the debugfs API, see
	  Documentation/DocBook/filesystems.

112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
	  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.

128 129 130 131 132
config DEBUG_SECTION_MISMATCH
	bool "Enable full Section mismatch analysis"
	help
	  The section mismatch analysis checks if there are illegal
	  references from one section to another section.
133 134
	  During linktime or runtime, some sections are dropped;
	  any use of code/data previously in these sections would
135
	  most likely result in an oops.
136
	  In the code, functions and variables are annotated with
137
	  __init, __cpuinit, etc. (see the full list in include/linux/init.h),
138
	  which results in the code/data being placed in specific sections.
139 140 141 142 143 144
	  The section mismatch analysis is always performed after a full
	  kernel build, and enabling this option causes the following
	  additional steps to occur:
	  - Add the option -fno-inline-functions-called-once to gcc commands.
	    When inlining a function annotated with __init in a non-init
	    function, we would lose the section information and thus
145
	    the analysis would not catch the illegal reference.
146 147 148 149
	    This option tells gcc to inline less (but it does result in
	    a larger kernel).
	  - Run the section mismatch analysis for each module/built-in.o file.
	    When we run the section mismatch analysis on vmlinux.o, we
150
	    lose valueble information about where the mismatch was
151 152
	    introduced.
	    Running the analysis for each module/built-in.o file
153 154 155 156 157
	    tells where the mismatch happens much closer to the
	    source. The drawback is that the same mismatch is
	    reported at least twice.
	  - Enable verbose reporting from modpost in order to help resolve
	    the section mismatches that are reported.
158

159 160 161 162 163 164
config DEBUG_KERNEL
	bool "Kernel debugging"
	help
	  Say Y here if you are developing drivers or trying to debug and
	  identify kernel problems.

D
David Woodhouse 已提交
165 166 167 168 169 170 171 172 173
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.

174 175
config LOCKUP_DETECTOR
	bool "Detect Hard and Soft Lockups"
176
	depends on DEBUG_KERNEL && !S390
I
Ingo Molnar 已提交
177
	help
178 179 180 181
	  Say Y here to enable the kernel to act as a watchdog to detect
	  hard and soft lockups.

	  Softlockups are bugs that cause the kernel to loop in kernel
182
	  mode for more than 20 seconds, without giving other tasks a
183 184
	  chance to run.  The current stack trace is displayed upon
	  detection and the system will stay locked up.
I
Ingo Molnar 已提交
185

186
	  Hardlockups are bugs that cause the CPU to loop in kernel mode
187
	  for more than 10 seconds, without letting other interrupts have a
188 189
	  chance to run.  The current stack trace is displayed upon detection
	  and the system will stay locked up.
I
Ingo Molnar 已提交
190

191
	  The overhead should be minimal.  A periodic hrtimer runs to
192 193 194 195 196
	  generate interrupts and kick the watchdog task every 4 seconds.
	  An NMI is generated every 10 seconds or so to check for hardlockups.

	  The frequency of hrtimer and NMI events and the soft and hard lockup
	  thresholds can be controlled through the sysctl watchdog_thresh.
I
Ingo Molnar 已提交
197

198
config HARDLOCKUP_DETECTOR
199 200 201
	def_bool y
	depends on LOCKUP_DETECTOR && !HAVE_NMI_WATCHDOG
	depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
I
Ingo Molnar 已提交
202

203 204
config BOOTPARAM_HARDLOCKUP_PANIC
	bool "Panic (Reboot) On Hard Lockups"
205
	depends on HARDLOCKUP_DETECTOR
206 207 208
	help
	  Say Y here to enable the kernel to panic on "hard lockups",
	  which are bugs that cause the kernel to loop in kernel
209 210
	  mode with interrupts disabled for more than 10 seconds (configurable
	  using the watchdog_thresh sysctl).
211 212 213 214 215

	  Say N if unsure.

config BOOTPARAM_HARDLOCKUP_PANIC_VALUE
	int
216
	depends on HARDLOCKUP_DETECTOR
217 218 219 220
	range 0 1
	default 0 if !BOOTPARAM_HARDLOCKUP_PANIC
	default 1 if BOOTPARAM_HARDLOCKUP_PANIC

I
Ingo Molnar 已提交
221 222
config BOOTPARAM_SOFTLOCKUP_PANIC
	bool "Panic (Reboot) On Soft Lockups"
223
	depends on LOCKUP_DETECTOR
I
Ingo Molnar 已提交
224 225 226
	help
	  Say Y here to enable the kernel to panic on "soft lockups",
	  which are bugs that cause the kernel to loop in kernel
227 228
	  mode for more than 20 seconds (configurable using the watchdog_thresh
	  sysctl), without giving other tasks a chance to run.
I
Ingo Molnar 已提交
229 230 231 232 233 234 235 236 237 238 239

	  The panic can be used in combination with panic_timeout,
	  to cause the system to reboot automatically after a
	  lockup has been detected. This feature is useful for
	  high-availability systems that have uptime guarantees and
	  where a lockup must be resolved ASAP.

	  Say N if unsure.

config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
	int
240
	depends on LOCKUP_DETECTOR
I
Ingo Molnar 已提交
241 242 243 244
	range 0 1
	default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC
	default 1 if BOOTPARAM_SOFTLOCKUP_PANIC

245
config PANIC_ON_OOPS
246
	bool "Panic on Oops"
247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263
	help
	  Say Y here to enable the kernel to panic when it oopses. This
	  has the same effect as setting oops=panic on the kernel command
	  line.

	  This feature is useful to ensure that the kernel does not do
	  anything erroneous after an oops which could result in data
	  corruption or other issues.

	  Say N if unsure.

config PANIC_ON_OOPS_VALUE
	int
	range 0 1
	default 0 if !PANIC_ON_OOPS
	default 1 if PANIC_ON_OOPS

264 265 266
config DETECT_HUNG_TASK
	bool "Detect Hung Tasks"
	depends on DEBUG_KERNEL
267
	default LOCKUP_DETECTOR
268 269 270 271 272 273 274 275 276 277 278
	help
	  Say Y here to enable the kernel to detect "hung tasks",
	  which are bugs that cause the task to be stuck in
	  uninterruptible "D" state indefinitiley.

	  When a hung task is detected, the kernel will print the
	  current stack trace (which you should report), but the
	  task will stay in uninterruptible state. If lockdep is
	  enabled then all held locks will also be reported. This
	  feature has negligible overhead.

279 280 281 282 283 284 285 286 287
config DEFAULT_HUNG_TASK_TIMEOUT
	int "Default timeout for hung task detection (in seconds)"
	depends on DETECT_HUNG_TASK
	default 120
	help
	  This option controls the default timeout (in seconds) used
	  to determine when a task has become non-responsive and should
	  be considered hung.

288 289 290
	  It can be adjusted at runtime via the kernel.hung_task_timeout_secs
	  sysctl or by writing a value to
	  /proc/sys/kernel/hung_task_timeout_secs.
291 292 293 294

	  A timeout of 0 disables the check.  The default is two minutes.
	  Keeping the default should be fine in most cases.

295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317
config BOOTPARAM_HUNG_TASK_PANIC
	bool "Panic (Reboot) On Hung Tasks"
	depends on DETECT_HUNG_TASK
	help
	  Say Y here to enable the kernel to panic on "hung tasks",
	  which are bugs that cause the kernel to leave a task stuck
	  in uninterruptible "D" state.

	  The panic can be used in combination with panic_timeout,
	  to cause the system to reboot automatically after a
	  hung task has been detected. This feature is useful for
	  high-availability systems that have uptime guarantees and
	  where a hung tasks must be resolved ASAP.

	  Say N if unsure.

config BOOTPARAM_HUNG_TASK_PANIC_VALUE
	int
	depends on DETECT_HUNG_TASK
	range 0 1
	default 0 if !BOOTPARAM_HUNG_TASK_PANIC
	default 1 if BOOTPARAM_HUNG_TASK_PANIC

318 319 320 321 322 323 324 325 326
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.

L
Linus Torvalds 已提交
327 328 329 330 331 332 333 334 335 336 337 338
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.

339 340 341 342 343 344 345 346 347
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
I
Ingo Molnar 已提交
348 349 350 351
	  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).
352

353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375
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.

376 377 378 379 380 381 382 383
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.

384 385 386 387 388 389 390 391
config DEBUG_OBJECTS_WORK
	bool "Debug work objects"
	depends on DEBUG_OBJECTS
	help
	  If you say Y here, additional code will be inserted into the
	  work queue routines to track the life time of work objects and
	  validate the work operations.

392 393
config DEBUG_OBJECTS_RCU_HEAD
	bool "Debug RCU callbacks objects"
394
	depends on DEBUG_OBJECTS
395 396 397
	help
	  Enable this to turn on debugging of RCU list heads (call_rcu() usage).

T
Tejun Heo 已提交
398 399 400 401 402 403 404 405
config DEBUG_OBJECTS_PERCPU_COUNTER
	bool "Debug percpu counter objects"
	depends on DEBUG_OBJECTS
	help
	  If you say Y here, additional code will be inserted into the
	  percpu counter routines to track the life time of percpu counter
	  objects and validate the percpu counter operations.

406 407 408 409 410 411 412 413
config DEBUG_OBJECTS_ENABLE_DEFAULT
	int "debug_objects bootup default value (0-1)"
        range 0 1
        default "1"
        depends on DEBUG_OBJECTS
        help
          Debug objects boot parameter default value

L
Linus Torvalds 已提交
414
config DEBUG_SLAB
415
	bool "Debug slab memory allocations"
416
	depends on DEBUG_KERNEL && SLAB && !KMEMCHECK
L
Linus Torvalds 已提交
417 418 419 420 421
	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.

422 423 424 425
config DEBUG_SLAB_LEAK
	bool "Memory leak debugging"
	depends on DEBUG_SLAB

426 427
config SLUB_DEBUG_ON
	bool "SLUB debugging on by default"
428
	depends on SLUB && SLUB_DEBUG && !KMEMCHECK
429 430 431 432 433 434 435 436 437 438
	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=-".

439 440 441
config SLUB_STATS
	default n
	bool "Enable SLUB performance statistics"
442
	depends on SLUB && SYSFS
443 444 445 446 447 448 449 450 451
	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

452 453 454
config HAVE_DEBUG_KMEMLEAK
	bool

455 456
config DEBUG_KMEMLEAK
	bool "Kernel memory leak detector"
457
	depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK
458
	select DEBUG_FS
459 460
	select STACKTRACE if STACKTRACE_SUPPORT
	select KALLSYMS
461
	select CRC32
462 463 464 465 466 467 468 469 470 471
	help
	  Say Y here if you want to enable the memory leak
	  detector. The memory allocation/freeing is traced in a way
	  similar to the Boehm's conservative garbage collector, the
	  difference being that the orphan objects are not freed but
	  only shown in /sys/kernel/debug/kmemleak. Enabling this
	  feature will introduce an overhead to memory
	  allocations. See Documentation/kmemleak.txt for more
	  details.

472 473 474
	  Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances
	  of finding leaks due to the slab objects poisoning.

475 476 477
	  In order to access the kmemleak file, debugfs needs to be
	  mounted (usually at /sys/kernel/debug).

478 479 480
config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
	int "Maximum kmemleak early log entries"
	depends on DEBUG_KMEMLEAK
H
Heiko Carstens 已提交
481
	range 200 40000
482 483 484 485 486 487 488 489
	default 400
	help
	  Kmemleak must track all the memory allocations to avoid
	  reporting false positives. Since memory may be allocated or
	  freed before kmemleak is initialised, an early log buffer is
	  used to store these actions. If kmemleak reports "early log
	  buffer exceeded", please increase this value.

490 491
config DEBUG_KMEMLEAK_TEST
	tristate "Simple test for the kernel memory leak detector"
492
	depends on DEBUG_KMEMLEAK && m
493
	help
494
	  This option enables a module that explicitly leaks memory.
495 496 497

	  If unsure, say N.

498 499 500 501 502 503 504
config DEBUG_KMEMLEAK_DEFAULT_OFF
	bool "Default kmemleak to off"
	depends on DEBUG_KMEMLEAK
	help
	  Say Y here to disable kmemleak by default. It can then be enabled
	  on the command line via kmemleak=on.

L
Linus Torvalds 已提交
505 506
config DEBUG_PREEMPT
	bool "Debug preemptible kernel"
507
	depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
L
Linus Torvalds 已提交
508 509 510 511 512 513 514
	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.

I
Ingo Molnar 已提交
515 516 517 518 519 520 521 522 523 524 525 526
config DEBUG_RT_MUTEXES
	bool "RT Mutex debugging, deadlock detection"
	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

527 528
config RT_MUTEX_TESTER
	bool "Built-in scriptable tester for rt-mutexes"
529
	depends on DEBUG_KERNEL && RT_MUTEXES
530 531 532
	help
	  This option enables a rt-mutex tester.

L
Linus Torvalds 已提交
533
config DEBUG_SPINLOCK
I
Ingo Molnar 已提交
534
	bool "Spinlock and rw-lock debugging: basic checks"
L
Linus Torvalds 已提交
535
	depends on DEBUG_KERNEL
536
	select UNINLINE_SPIN_UNLOCK
L
Linus Torvalds 已提交
537 538 539 540 541 542
	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.

I
Ingo Molnar 已提交
543 544 545 546 547 548 549 550 551
config DEBUG_MUTEXES
	bool "Mutex debugging: basic checks"
	depends on DEBUG_KERNEL
	help
	 This feature allows mutex semantics violations to be detected and
	 reported.

config DEBUG_LOCK_ALLOC
	bool "Lock debugging: detect incorrect freeing of live locks"
552
	depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
I
Ingo Molnar 已提交
553 554 555 556 557 558 559 560 561 562 563 564 565
	select DEBUG_SPINLOCK
	select DEBUG_MUTEXES
	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"
566
	depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
I
Ingo Molnar 已提交
567 568 569 570
	select LOCKDEP
	select DEBUG_SPINLOCK
	select DEBUG_MUTEXES
	select DEBUG_LOCK_ALLOC
571
	select TRACE_IRQFLAGS
I
Ingo Molnar 已提交
572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608
	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
609
	depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
I
Ingo Molnar 已提交
610
	select STACKTRACE
611
	select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE
I
Ingo Molnar 已提交
612 613 614
	select KALLSYMS
	select KALLSYMS_ALL

P
Peter Zijlstra 已提交
615
config LOCK_STAT
D
Danny ter Haar 已提交
616
	bool "Lock usage statistics"
P
Peter Zijlstra 已提交
617 618 619 620 621 622 623 624 625
	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

P
Peter Zijlstra 已提交
626 627
	 For more details, see Documentation/lockstat.txt

628 629 630 631
	 This also enables lock events required by "perf lock",
	 subcommand of perf.
	 If you want to use "perf lock", you also need to turn on
	 CONFIG_EVENT_TRACING.
632 633

	 CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
634
	 (CONFIG_LOCKDEP defines "acquire" and "release" events.)
635

I
Ingo Molnar 已提交
636 637
config DEBUG_LOCKDEP
	bool "Lock dependency engine debugging"
638
	depends on DEBUG_KERNEL && LOCKDEP
I
Ingo Molnar 已提交
639 640 641 642 643 644 645
	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
	bool
646 647 648
	help
	  Enables hooks to interrupt enabling and disabling for
	  either tracing or lock debugging.
I
Ingo Molnar 已提交
649

650 651
config DEBUG_ATOMIC_SLEEP
	bool "Sleep inside atomic section checking"
652
	select PREEMPT_COUNT
L
Linus Torvalds 已提交
653 654 655
	depends on DEBUG_KERNEL
	help
	  If you say Y here, various routines which may sleep will become very
656 657 658
	  noisy if they are called inside atomic sections: when a spinlock is
	  held, inside an rcu read side critical section, inside preempt disabled
	  sections, inside an interrupt, etc...
L
Linus Torvalds 已提交
659

660 661 662 663 664 665 666 667 668 669 670
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.

671 672 673 674
config STACKTRACE
	bool
	depends on STACKTRACE_SUPPORT

675 676
config DEBUG_STACK_USAGE
	bool "Stack utilization instrumentation"
677
	depends on DEBUG_KERNEL && !IA64 && !PARISC && !METAG
678 679 680 681 682 683
	help
	  Enables the display of the minimum amount of free stack which each
	  task has ever had available in the sysrq-T and sysrq-P debug output.

	  This option will slow down process creation somewhat.

L
Linus Torvalds 已提交
684 685 686 687 688 689 690 691 692 693 694 695 696 697
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.

698 699 700
config HAVE_DEBUG_BUGVERBOSE
	bool

L
Linus Torvalds 已提交
701
config DEBUG_BUGVERBOSE
702
	bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
703
	depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE)
704
	default y
L
Linus Torvalds 已提交
705 706 707 708 709 710 711 712 713 714 715
	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.
716 717 718
	  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.
L
Linus Torvalds 已提交
719 720 721 722
	  Say Y here only if you plan to debug the kernel.

	  If unsure, say N.

723 724 725 726 727 728 729 730 731 732 733 734 735
config DEBUG_INFO_REDUCED
	bool "Reduce debugging information"
	depends on DEBUG_INFO
	help
	  If you say Y here gcc is instructed to generate less debugging
	  information for structure types. This means that tools that
	  need full debugging information (like kgdb or systemtap) won't
	  be happy. But if you merely need debugging information to
	  resolve line numbers there is no loss. Advantage is that
	  build directory object sizes shrink dramatically over a full
	  DEBUG_INFO build and compile times are reduced too.
	  Only works with newer gcc versions.

736 737 738 739
config DEBUG_VM
	bool "Debug VM"
	depends on DEBUG_KERNEL
	help
N
Nick Piggin 已提交
740 741
	  Enable this to turn on extended checks in the virtual-memory system
          that may impact performance.
742 743 744

	  If unsure, say N.

745 746 747 748 749 750 751 752 753
config DEBUG_VM_RB
	bool "Debug VM red-black trees"
	depends on DEBUG_VM
	help
	  Enable this to turn on more extended checks in the virtual-memory
	  system that may impact performance.

	  If unsure, say N.

J
Jiri Slaby 已提交
754 755 756 757 758 759 760 761 762
config DEBUG_VIRTUAL
	bool "Debug VM translations"
	depends on DEBUG_KERNEL && X86
	help
	  Enable some costly sanity checks in virtual to page code. This can
	  catch mistakes with virt_to_page() and friends.

	  If unsure, say N.

763 764 765 766 767 768 769
config DEBUG_NOMMU_REGIONS
	bool "Debug the global anon/private NOMMU mapping region tree"
	depends on DEBUG_KERNEL && !MMU
	help
	  This option causes the global tree of anonymous and private mapping
	  regions to be regularly checked for invalid topology.

770 771 772 773 774 775 776 777 778 779
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.

780
config DEBUG_MEMORY_INIT
781 782
	bool "Debug memory initialisation" if EXPERT
	default !EXPERT
783 784 785 786 787 788 789 790 791
	help
	  Enable this for additional checks during memory initialisation.
	  The sanity checks verify aspects of the VM such as the memory model
	  and other information provided by the architecture. Verbose
	  information will be printed at KERN_DEBUG loglevel depending
	  on the mminit_loglevel= command-line option.

	  If unsure, say Y

792 793 794 795 796 797 798 799 800
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.

801 802 803 804 805 806 807 808 809
config TEST_LIST_SORT
	bool "Linked list sorting test"
	depends on DEBUG_KERNEL
	help
	  Enable this to turn on 'list_sort()' function test. This test is
	  executed only once during system boot, so affects only boot time.

	  If unsure, say N.

J
Jens Axboe 已提交
810 811 812 813 814 815 816 817 818 819
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.

820 821 822 823 824 825 826 827 828 829
config DEBUG_NOTIFIERS
	bool "Debug notifier call chains"
	depends on DEBUG_KERNEL
	help
	  Enable this to turn on sanity checking for notifier call chains.
	  This is most useful for kernel developers to make sure that
	  modules properly unregister themselves from notifier chains.
	  This is a relatively cheap check but if you care about maximum
	  performance, say N.

830 831 832 833 834 835 836 837 838 839 840 841 842 843 844
config DEBUG_CREDENTIALS
	bool "Debug credential management"
	depends on DEBUG_KERNEL
	help
	  Enable this to turn on some debug checking for credential
	  management.  The additional code keeps track of the number of
	  pointers from task_structs to any given cred struct, and checks to
	  see that this number never exceeds the usage count of the cred
	  struct.

	  Furthermore, if SELinux is enabled, this also checks that the
	  security pointer in the cred struct is never seen to be invalid.

	  If unsure, say N.

845 846
#
# Select this config option from the architecture Kconfig, if it
847
# is preferred to always offer frame pointers as a config
848 849 850 851 852 853
# option on the architecture (regardless of KERNEL_DEBUG):
#
config ARCH_WANT_FRAME_POINTERS
	bool
	help

L
Linus Torvalds 已提交
854 855
config FRAME_POINTER
	bool "Compile the kernel with frame pointers"
856
	depends on DEBUG_KERNEL && \
857
		(CRIS || M68K || FRV || UML || \
858
		 AVR32 || SUPERH || BLACKFIN || MN10300 || METAG) || \
859 860 861 862 863 864
		ARCH_WANT_FRAME_POINTERS
	default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
	help
	  If you say Y here the resulting kernel image will be slightly
	  larger and slower, but it gives very useful debugging information
	  in case of kernel bugs. (precise oopses/stacktraces/warnings)
L
Linus Torvalds 已提交
865

R
Randy Dunlap 已提交
866 867 868 869 870 871 872 873 874 875 876 877 878 879 880
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.
881
	  BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
R
Randy Dunlap 已提交
882 883
	  what it believes to be lockup conditions.

884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940
menu "RCU Debugging"

config PROVE_RCU
	bool "RCU debugging: prove RCU correctness"
	depends on PROVE_LOCKING
	default n
	help
	 This feature enables lockdep extensions that check for correct
	 use of RCU APIs.  This is currently under development.  Say Y
	 if you want to debug RCU usage or help work on the PROVE_RCU
	 feature.

	 Say N if you are unsure.

config PROVE_RCU_REPEATEDLY
	bool "RCU debugging: don't disable PROVE_RCU on first splat"
	depends on PROVE_RCU
	default n
	help
	 By itself, PROVE_RCU will disable checking upon issuing the
	 first warning (or "splat").  This feature prevents such
	 disabling, allowing multiple RCU-lockdep warnings to be printed
	 on a single reboot.

	 Say Y to allow multiple RCU-lockdep warnings per boot.

	 Say N if you are unsure.

config PROVE_RCU_DELAY
	bool "RCU debugging: preemptible RCU race provocation"
	depends on DEBUG_KERNEL && PREEMPT_RCU
	default n
	help
	 There is a class of races that involve an unlikely preemption
	 of __rcu_read_unlock() just after ->rcu_read_lock_nesting has
	 been set to INT_MIN.  This feature inserts a delay at that
	 point to increase the probability of these races.

	 Say Y to increase probability of preemption of __rcu_read_unlock().

	 Say N if you are unsure.

config SPARSE_RCU_POINTER
	bool "RCU debugging: sparse-based checks for pointer usage"
	default n
	help
	 This feature enables the __rcu sparse annotation for
	 RCU-protected pointers.  This annotation will cause sparse
	 to flag any non-RCU used of annotated pointers.  This can be
	 helpful when debugging RCU usage.  Please note that this feature
	 is not intended to enforce code cleanliness; it is instead merely
	 a debugging aid.

	 Say Y to make sparse flag questionable use of RCU-protected pointers

	 Say N if you are unsure.

941 942 943 944 945 946 947 948 949
config RCU_TORTURE_TEST
	tristate "torture tests for RCU"
	depends on DEBUG_KERNEL
	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.

950 951
	  Say Y here if you want RCU torture tests to be built into
	  the kernel.
952 953
	  Say M if you want the RCU torture tests to build as a module.
	  Say N if you are unsure.
954

955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971
config RCU_TORTURE_TEST_RUNNABLE
	bool "torture tests for RCU runnable by default"
	depends on RCU_TORTURE_TEST = y
	default n
	help
	  This option provides a way to build the RCU torture tests
	  directly into the kernel without them starting up at boot
	  time.  You can use /proc/sys/kernel/rcutorture_runnable
	  to manually override this setting.  This /proc file is
	  available only when the RCU torture tests have been built
	  into the kernel.

	  Say Y here if you want the RCU torture tests to start during
	  boot (you probably don't).
	  Say N here if you want the RCU torture tests to start only
	  after being manually enabled via /proc.

972 973
config RCU_CPU_STALL_TIMEOUT
	int "RCU CPU stall timeout in seconds"
974
	depends on RCU_STALL_COMMON
975
	range 3 300
976
	default 21
977 978 979 980 981 982
	help
	  If a given RCU grace period extends more than the specified
	  number of seconds, a CPU stall warning is printed.  If the
	  RCU grace period persists, additional CPU stall warnings are
	  printed at more widely spaced intervals.

983 984
config RCU_CPU_STALL_VERBOSE
	bool "Print additional per-task information for RCU_CPU_STALL_DETECTOR"
985
	depends on TREE_PREEMPT_RCU
986
	default y
987 988 989
	help
	  This option causes RCU to printk detailed per-task information
	  for any tasks that are stalling the current RCU grace period.
990 991 992

	  Say N if you are unsure.

993 994
	  Say Y if you want to enable such checks.

995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008
config RCU_CPU_STALL_INFO
	bool "Print additional diagnostics on RCU CPU stall"
	depends on (TREE_RCU || TREE_PREEMPT_RCU) && DEBUG_KERNEL
	default n
	help
	  For each stalled CPU that is aware of the current RCU grace
	  period, print out additional per-CPU diagnostic information
	  regarding scheduling-clock ticks, idle state, and,
	  for RCU_FAST_NO_HZ kernels, idle-entry state.

	  Say N if you are unsure.

	  Say Y if you want to enable such diagnostics.

1009 1010 1011
config RCU_TRACE
	bool "Enable tracing for RCU"
	depends on DEBUG_KERNEL
1012
	select TRACE_CLOCK
1013 1014 1015 1016 1017 1018 1019
	help
	  This option provides tracing in RCU which presents stats
	  in debugfs for debugging RCU implementation.

	  Say Y here if you want to enable RCU tracing
	  Say N if you are unsure.

1020 1021
endmenu # "RCU Debugging"

1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033
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.

1034 1035 1036 1037 1038 1039 1040 1041 1042 1043
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.

1044 1045 1046
	  Note that if you want to also test saved backtraces, you will
	  have to enable STACKTRACE as well.

1047 1048
	  Say N if you are unsure.

1049 1050 1051 1052
config DEBUG_BLOCK_EXT_DEVT
        bool "Force extended block device numbers and spread them"
	depends on DEBUG_KERNEL
	depends on BLOCK
1053
	default n
1054
	help
1055 1056 1057 1058 1059
	  BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
	  SOME DISTRIBUTIONS.  DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
	  YOU ARE DOING.  Distros, please enable this and fix whatever
	  is broken.

1060 1061 1062 1063 1064 1065 1066 1067
	  Conventionally, block device numbers are allocated from
	  predetermined contiguous area.  However, extended block area
	  may introduce non-contiguous block device numbers.  This
	  option forces most block device numbers to be allocated from
	  the extended space and spreads them to discover kernel or
	  userland code paths which assume predetermined contiguous
	  device number allocation.

1068 1069 1070 1071 1072 1073
	  Note that turning on this debug option shuffles all the
	  device numbers for all IDE and SCSI devices including libata
	  ones, so root partition specified using device number
	  directly (via rdev or root=MAJ:MIN) won't work anymore.
	  Textual device names (root=/dev/sdXn) will continue to work.

1074 1075
	  Say N if you are unsure.

1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090
config DEBUG_FORCE_WEAK_PER_CPU
	bool "Force weak per-cpu definitions"
	depends on DEBUG_KERNEL
	help
	  s390 and alpha require percpu variables in modules to be
	  defined weak to work around addressing range issue which
	  puts the following two restrictions on percpu variable
	  definitions.

	  1. percpu symbols must be unique whether static or not
	  2. percpu variables can't be defined inside a function

	  To ensure that generic code follows the above rules, this
	  option forces all percpu variables to be defined as weak.

1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101
config DEBUG_PER_CPU_MAPS
	bool "Debug access to per_cpu maps"
	depends on DEBUG_KERNEL
	depends on SMP
	help
	  Say Y to verify that the per_cpu map being accessed has
	  been set up. This adds a fair amount of code to kernel memory
	  and decreases performance.

	  Say N if unsure.

1102 1103
config LKDTM
	tristate "Linux Kernel Dump Test Tool Module"
1104
	depends on DEBUG_FS
C
Chris Snook 已提交
1105
	depends on BLOCK
1106 1107 1108 1109 1110 1111 1112 1113 1114
	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
1115
	Documentation/fault-injection/provoke-crashes.txt
1116

1117 1118 1119 1120 1121
config NOTIFIER_ERROR_INJECTION
	tristate "Notifier error injection"
	depends on DEBUG_KERNEL
	select DEBUG_FS
	help
1122
	  This option provides the ability to inject artificial errors to
1123 1124 1125 1126 1127
	  specified notifier chain callbacks. It is useful to test the error
	  handling of notifier call chain failures.

	  Say N if unsure.

1128 1129
config CPU_NOTIFIER_ERROR_INJECT
	tristate "CPU notifier error injection module"
1130
	depends on HOTPLUG_CPU && NOTIFIER_ERROR_INJECTION
1131 1132
	help
	  This option provides a kernel module that can be used to test
1133
	  the error handling of the cpu notifiers by injecting artificial
1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145
	  errors to CPU notifier chain callbacks.  It is controlled through
	  debugfs interface under /sys/kernel/debug/notifier-error-inject/cpu

	  If the notifier call chain should be failed with some events
	  notified, write the error code to "actions/<notifier event>/error".

	  Example: Inject CPU offline error (-1 == -EPERM)

	  # cd /sys/kernel/debug/notifier-error-inject/cpu
	  # echo -1 > actions/CPU_DOWN_PREPARE/error
	  # echo 0 > /sys/devices/system/cpu/cpu1/online
	  bash: echo: write error: Operation not permitted
1146 1147 1148 1149 1150 1151

	  To compile this code as a module, choose M here: the module will
	  be called cpu-notifier-error-inject.

	  If unsure, say N.

1152 1153 1154 1155 1156
config PM_NOTIFIER_ERROR_INJECT
	tristate "PM notifier error injection module"
	depends on PM && NOTIFIER_ERROR_INJECTION
	default m if PM_DEBUG
	help
1157
	  This option provides the ability to inject artificial errors to
1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175
	  PM notifier chain callbacks.  It is controlled through debugfs
	  interface /sys/kernel/debug/notifier-error-inject/pm

	  If the notifier call chain should be failed with some events
	  notified, write the error code to "actions/<notifier event>/error".

	  Example: Inject PM suspend error (-12 = -ENOMEM)

	  # cd /sys/kernel/debug/notifier-error-inject/pm/
	  # echo -12 > actions/PM_SUSPEND_PREPARE/error
	  # echo mem > /sys/power/state
	  bash: echo: write error: Cannot allocate memory

	  To compile this code as a module, choose M here: the module will
	  be called pm-notifier-error-inject.

	  If unsure, say N.

1176 1177 1178 1179
config MEMORY_NOTIFIER_ERROR_INJECT
	tristate "Memory hotplug notifier error injection module"
	depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION
	help
1180
	  This option provides the ability to inject artificial errors to
1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198
	  memory hotplug notifier chain callbacks.  It is controlled through
	  debugfs interface under /sys/kernel/debug/notifier-error-inject/memory

	  If the notifier call chain should be failed with some events
	  notified, write the error code to "actions/<notifier event>/error".

	  Example: Inject memory hotplug offline error (-12 == -ENOMEM)

	  # cd /sys/kernel/debug/notifier-error-inject/memory
	  # echo -12 > actions/MEM_GOING_OFFLINE/error
	  # echo offline > /sys/devices/system/memory/memoryXXX/state
	  bash: echo: write error: Cannot allocate memory

	  To compile this code as a module, choose M here: the module will
	  be called pSeries-reconfig-notifier-error-inject.

	  If unsure, say N.

1199 1200 1201
config OF_RECONFIG_NOTIFIER_ERROR_INJECT
	tristate "OF reconfig notifier error injection module"
	depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION
1202
	help
1203
	  This option provides the ability to inject artificial errors to
1204
	  OF reconfig notifier chain callbacks.  It is controlled
1205
	  through debugfs interface under
1206
	  /sys/kernel/debug/notifier-error-inject/OF-reconfig/
1207 1208 1209 1210 1211 1212 1213 1214 1215

	  If the notifier call chain should be failed with some events
	  notified, write the error code to "actions/<notifier event>/error".

	  To compile this code as a module, choose M here: the module will
	  be called memory-notifier-error-inject.

	  If unsure, say N.

1216
config FAULT_INJECTION
1217 1218
	bool "Fault-injection framework"
	depends on DEBUG_KERNEL
1219 1220 1221
	help
	  Provide fault-injection framework.
	  For more details, see Documentation/fault-injection/.
1222

1223
config FAILSLAB
1224 1225
	bool "Fault-injection capability for kmalloc"
	depends on FAULT_INJECTION
A
Akinobu Mita 已提交
1226
	depends on SLAB || SLUB
1227
	help
1228
	  Provide fault-injection capability for kmalloc.
1229

1230 1231
config FAIL_PAGE_ALLOC
	bool "Fault-injection capabilitiy for alloc_pages()"
1232
	depends on FAULT_INJECTION
1233
	help
1234
	  Provide fault-injection capability for alloc_pages().
1235

1236
config FAIL_MAKE_REQUEST
D
Dave Jones 已提交
1237
	bool "Fault-injection capability for disk IO"
1238
	depends on FAULT_INJECTION && BLOCK
1239
	help
1240
	  Provide fault-injection capability for disk IO.
1241

1242
config FAIL_IO_TIMEOUT
1243
	bool "Fault-injection capability for faking disk interrupts"
1244 1245 1246 1247 1248 1249 1250 1251 1252
	depends on FAULT_INJECTION && BLOCK
	help
	  Provide fault-injection capability on end IO handling. This
	  will make the block layer "forget" an interrupt as configured,
	  thus exercising the error handling.

	  Only works with drivers that use the generic timeout handling,
	  for others it wont do anything.

P
Per Forlin 已提交
1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263
config FAIL_MMC_REQUEST
	bool "Fault-injection capability for MMC IO"
	select DEBUG_FS
	depends on FAULT_INJECTION && MMC
	help
	  Provide fault-injection capability for MMC IO.
	  This will make the mmc core return data errors. This is
	  useful to test the error handling in the mmc block device
	  and to test how the mmc host driver handles retries from
	  the block device.

1264 1265
config FAULT_INJECTION_DEBUG_FS
	bool "Debugfs entries for fault-injection capabilities"
1266
	depends on FAULT_INJECTION && SYSFS && DEBUG_FS
1267
	help
1268
	  Enable configuration of fault-injection capabilities via debugfs.
1269 1270 1271 1272

config FAULT_INJECTION_STACKTRACE_FILTER
	bool "stacktrace filter for fault-injection capabilities"
	depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
1273
	depends on !X86_64
1274
	select STACKTRACE
1275
	select FRAME_POINTER if !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND
1276 1277
	help
	  Provide stacktrace filter for fault-injection capabilities
M
Mathieu Desnoyers 已提交
1278

A
Arjan van de Ven 已提交
1279 1280
config LATENCYTOP
	bool "Latency measuring infrastructure"
1281 1282 1283 1284
	depends on HAVE_LATENCYTOP_SUPPORT
	depends on DEBUG_KERNEL
	depends on STACKTRACE_SUPPORT
	depends on PROC_FS
1285
	select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND
A
Arjan van de Ven 已提交
1286 1287 1288 1289 1290 1291 1292 1293 1294
	select KALLSYMS
	select KALLSYMS_ALL
	select STACKTRACE
	select SCHEDSTATS
	select SCHED_DEBUG
	help
	  Enable this option if you want to use the LatencyTOP tool
	  to find out which userspace is blocking on what kernel operations.

A
Akinobu Mita 已提交
1295
source mm/Kconfig.debug
1296 1297
source kernel/trace/Kconfig

1298 1299 1300 1301 1302 1303 1304
config RBTREE_TEST
	tristate "Red-Black tree test"
	depends on m && DEBUG_KERNEL
	help
	  A benchmark measuring the performance of the rbtree library.
	  Also includes rbtree invariant checks.

1305 1306 1307 1308 1309 1310
config INTERVAL_TREE_TEST
	tristate "Interval tree test"
	depends on m && DEBUG_KERNEL
	help
	  A benchmark measuring the performance of the interval tree library

1311
config PROVIDE_OHCI1394_DMA_INIT
1312
	bool "Remote debugging over FireWire early on boot"
1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338
	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.
A
Arjan van de Ven 已提交
1339

1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350
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.

1351
config BUILD_DOCSRC
1352 1353 1354 1355 1356 1357 1358 1359
	bool "Build targets in Documentation/ tree"
	depends on HEADERS_CHECK
	help
	  This option attempts to build objects from the source files in the
	  kernel Documentation/ tree.

	  Say N if you are unsure.

1360
config DYNAMIC_DEBUG
J
Jason Baron 已提交
1361
	bool "Enable dynamic printk() support"
1362 1363
	default n
	depends on PRINTK
J
Jason Baron 已提交
1364
	depends on DEBUG_FS
1365 1366 1367 1368
	help

	  Compiles debug level messages into the kernel, which would not
	  otherwise be available at runtime. These messages can then be
J
Jason Baron 已提交
1369 1370
	  enabled/disabled based on various levels of scope - per source file,
	  function, module, format string, and line number. This mechanism
1371 1372 1373 1374 1375 1376 1377
	  implicitly compiles in all pr_debug() and dev_dbg() calls, which
	  enlarges the kernel text size by about 2%.

	  If a source file is compiled with DEBUG flag set, any
	  pr_debug() calls in it are enabled by default, but can be
	  disabled at runtime as below.  Note that DEBUG flag is
	  turned on by many CONFIG_*DEBUG* options.
1378 1379 1380

	  Usage:

1381
	  Dynamic debugging is controlled via the 'dynamic_debug/control' file,
J
Jason Baron 已提交
1382 1383
	  which is contained in the 'debugfs' filesystem. Thus, the debugfs
	  filesystem must first be mounted before making use of this feature.
1384
	  We refer the control file as: <debugfs>/dynamic_debug/control. This
J
Jason Baron 已提交
1385 1386
	  file contains a list of the debug statements that can be enabled. The
	  format for each line of the file is:
1387

J
Jason Baron 已提交
1388
		filename:lineno [module]function flags format
1389

J
Jason Baron 已提交
1390 1391 1392 1393
	  filename : source file of the debug statement
	  lineno : line number of the debug statement
	  module : module that contains the debug statement
	  function : function that contains the debug statement
1394
          flags : '=p' means the line is turned 'on' for printing
J
Jason Baron 已提交
1395
          format : the format used for the debug statement
1396 1397 1398

	  From a live system:

1399
		nullarbor:~ # cat <debugfs>/dynamic_debug/control
J
Jason Baron 已提交
1400
		# filename:lineno [module]function flags format
1401 1402 1403
		fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012"
		fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012"
		fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012"
1404

J
Jason Baron 已提交
1405
	  Example usage:
1406

J
Jason Baron 已提交
1407 1408
		// enable the message at line 1603 of file svcsock.c
		nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
1409
						<debugfs>/dynamic_debug/control
1410

J
Jason Baron 已提交
1411 1412
		// enable all the messages in file svcsock.c
		nullarbor:~ # echo -n 'file svcsock.c +p' >
1413
						<debugfs>/dynamic_debug/control
1414

J
Jason Baron 已提交
1415 1416
		// enable all the messages in the NFS server module
		nullarbor:~ # echo -n 'module nfsd +p' >
1417
						<debugfs>/dynamic_debug/control
1418

J
Jason Baron 已提交
1419 1420
		// enable all 12 messages in the function svc_process()
		nullarbor:~ # echo -n 'func svc_process +p' >
1421
						<debugfs>/dynamic_debug/control
1422

J
Jason Baron 已提交
1423 1424
		// disable all 12 messages in the function svc_process()
		nullarbor:~ # echo -n 'func svc_process -p' >
1425
						<debugfs>/dynamic_debug/control
1426

J
Jason Baron 已提交
1427
	  See Documentation/dynamic-debug-howto.txt for additional information.
1428

J
Joerg Roedel 已提交
1429 1430 1431 1432 1433 1434 1435 1436 1437 1438
config DMA_API_DEBUG
	bool "Enable debugging of DMA-API usage"
	depends on HAVE_DMA_API_DEBUG
	help
	  Enable this option to debug the use of the DMA API by device drivers.
	  With this option you will be able to detect common bugs in device
	  drivers like double-freeing of DMA mappings or freeing mappings that
	  were never allocated.
	  This option causes a performance degredation.  Use only if you want
	  to debug device drivers. If unsure, say N.
1439

1440 1441 1442 1443 1444 1445 1446
config ATOMIC64_SELFTEST
	bool "Perform an atomic64_t self-test at boot"
	help
	  Enable this option to test the atomic64_t functions at boot.

	  If unsure, say N.

1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459
config ASYNC_RAID6_TEST
	tristate "Self test for hardware accelerated raid6 recovery"
	depends on ASYNC_RAID6_RECOV
	select ASYNC_MEMCPY
	---help---
	  This is a one-shot self test that permutes through the
	  recovery of all the possible two disk failure scenarios for a
	  N-disk array.  Recovery is performed with the asynchronous
	  raid6 recovery routines, and will optionally use an offload
	  engine if one is available.

	  If unsure, say N.

M
Mathieu Desnoyers 已提交
1460
source "samples/Kconfig"
J
Jason Wessel 已提交
1461 1462

source "lib/Kconfig.kgdb"
1463 1464

source "lib/Kconfig.kmemcheck"
1465

1466 1467 1468
config TEST_STRING_HELPERS
	tristate "Test functions located in the string_helpers module at runtime"

1469 1470
config TEST_KSTRTOX
	tristate "Test kstrto*() family of functions at runtime"