linux 2.6.16.38 w/ vs2.0.3-rc1

[linux-2.6.git] / lib / Kconfig.debug

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 212560a..a314e66 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -78,17 +78,13 @@ config SCHEDSTATS
          this adds.
 
 config DEBUG_SLAB
-       bool "Debug slab memory allocations"
+       bool "Debug memory allocations"
        depends on DEBUG_KERNEL && SLAB
        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.
 
-config DEBUG_SLAB_LEAK
-       bool "Memory leak debugging"
-       depends on DEBUG_SLAB
-
 config DEBUG_PREEMPT
        bool "Debug preemptible kernel"
        depends on DEBUG_KERNEL && PREEMPT
@@ -101,7 +97,7 @@ config DEBUG_PREEMPT
 
 config DEBUG_MUTEXES
        bool "Mutex debugging, deadlock detection"
-       default n
+       default y
        depends on DEBUG_KERNEL
        help
         This allows mutex semantics violations and mutex related deadlocks
@@ -157,9 +153,22 @@ config DEBUG_INFO
 
          If unsure, say N.
 
+config DEBUG_IOREMAP
+       bool "Enable ioremap() debugging"
+       depends on DEBUG_KERNEL && PARISC
+       help
+         Enabling this option will cause the kernel to distinguish between
+         ioremapped and physical addresses.  It will print a backtrace (at
+         most one every 10 seconds), hopefully allowing you to see which
+         drivers need work.  Fixing all these problems is a prerequisite
+         for turning on USE_HPPA_IOREMAP.  The warnings are harmless;
+         the kernel has enough information to fix the broken drivers
+         automatically, but we'd like to make it more efficient by not
+         having to do that.
+
 config DEBUG_FS
        bool "Debug Filesystem"
-       depends on SYSFS
+       depends on DEBUG_KERNEL && 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
@@ -186,16 +195,6 @@ config FRAME_POINTER
          some architectures or if you use external debuggers.
          If you don't debug the kernel, you can say N.
 
-config UNWIND_INFO
-       bool "Compile the kernel with frame unwind information"
-       depends on !IA64
-       depends on !MODULES || !(MIPS || PARISC || PPC || SUPERH || V850)
-       help
-         If you say Y here the resulting kernel image will be slightly larger
-         but not slower, and it will give very useful debugging information.
-         If you don't debug the kernel, you can say N, but we may not be able
-         to solve problems without frame unwind information or frame pointers.
-
 config FORCED_INLINING
        bool "Force gcc to inline functions marked 'inline'"
        depends on DEBUG_KERNEL
@@ -210,24 +209,6 @@ config FORCED_INLINING
          become the default in the future, until then this option is there to
          test gcc for this.
 
-config BOOT_DELAY
-       bool "Delay each boot message by N milliseconds"
-       depends on DEBUG_KERNEL
-       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_DELAY also may cause DETECT_SOFTLOCKUP to detect
-         what it believes to be lockup conditions.
-
 config RCU_TORTURE_TEST
        tristate "torture tests for RCU"
        depends on DEBUG_KERNEL