1.1 --- a/buildconfigs/linux-defconfig_xen0_x86_64	Thu Apr 06 09:40:15 2006 +0100
     1.2 +++ b/buildconfigs/linux-defconfig_xen0_x86_64	Thu Apr 06 09:47:58 2006 +0100
     1.3 @@ -1183,6 +1183,7 @@ CONFIG_DETECT_SOFTLOCKUP=y
     1.4  # CONFIG_DEBUG_SPINLOCK is not set
     1.5  # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
     1.6  # CONFIG_DEBUG_KOBJECT is not set
     1.7 +# CONFIG_DEBUG_INFO is not set
     1.8  # CONFIG_DEBUG_FS is not set
     1.9  # CONFIG_DEBUG_VM is not set
    1.10  CONFIG_FRAME_POINTER=y

     2.1 --- a/buildconfigs/linux-defconfig_xenU_x86_64	Thu Apr 06 09:40:15 2006 +0100
     2.2 +++ b/buildconfigs/linux-defconfig_xenU_x86_64	Thu Apr 06 09:47:58 2006 +0100
     2.3 @@ -1080,6 +1080,7 @@ CONFIG_DETECT_SOFTLOCKUP=y
     2.4  # CONFIG_DEBUG_SPINLOCK is not set
     2.5  # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
     2.6  # CONFIG_DEBUG_KOBJECT is not set
     2.7 +# CONFIG_DEBUG_INFO is not set
     2.8  # CONFIG_DEBUG_FS is not set
     2.9  # CONFIG_DEBUG_VM is not set
    2.10  CONFIG_FRAME_POINTER=y

     3.1 --- a/buildconfigs/linux-defconfig_xen_x86_64	Thu Apr 06 09:40:15 2006 +0100
     3.2 +++ b/buildconfigs/linux-defconfig_xen_x86_64	Thu Apr 06 09:47:58 2006 +0100
     3.3 @@ -2587,6 +2587,7 @@ CONFIG_DETECT_SOFTLOCKUP=y
     3.4  # CONFIG_DEBUG_SPINLOCK is not set
     3.5  # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
     3.6  # CONFIG_DEBUG_KOBJECT is not set
     3.7 +# CONFIG_DEBUG_INFO is not set
     3.8  # CONFIG_DEBUG_FS is not set
     3.9  # CONFIG_DEBUG_VM is not set
    3.10  # CONFIG_FRAME_POINTER is not set

     4.1 --- a/linux-2.6-xen-sparse/lib/Kconfig.debug	Thu Apr 06 09:40:15 2006 +0100
     4.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     4.3 @@ -1,224 +0,0 @@
     4.4 -
     4.5 -config PRINTK_TIME
     4.6 -	bool "Show timing information on printks"
     4.7 -	help
     4.8 -	  Selecting this option causes timing information to be
     4.9 -	  included in printk output.  This allows you to measure
    4.10 -	  the interval between kernel operations, including bootup
    4.11 -	  operations.  This is useful for identifying long delays
    4.12 -	  in kernel startup.
    4.13 -
    4.14 -
    4.15 -config MAGIC_SYSRQ
    4.16 -	bool "Magic SysRq key"
    4.17 -	depends on !UML
    4.18 -	help
    4.19 -	  If you say Y here, you will have some control over the system even
    4.20 -	  if the system crashes for example during kernel debugging (e.g., you
    4.21 -	  will be able to flush the buffer cache to disk, reboot the system
    4.22 -	  immediately or dump some status information). This is accomplished
    4.23 -	  by pressing various keys while holding SysRq (Alt+PrintScreen). It
    4.24 -	  also works on a serial console (on PC hardware at least), if you
    4.25 -	  send a BREAK and then within 5 seconds a command keypress. The
    4.26 -	  keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
    4.27 -	  unless you really know what this hack does.
    4.28 -
    4.29 -config DEBUG_KERNEL
    4.30 -	bool "Kernel debugging"
    4.31 -	help
    4.32 -	  Say Y here if you are developing drivers or trying to debug and
    4.33 -	  identify kernel problems.
    4.34 -
    4.35 -config LOG_BUF_SHIFT
    4.36 -	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
    4.37 -	range 12 21
    4.38 -	default 17 if S390
    4.39 -	default 16 if X86_NUMAQ || IA64
    4.40 -	default 15 if SMP
    4.41 -	default 14
    4.42 -	help
    4.43 -	  Select kernel log buffer size as a power of 2.
    4.44 -	  Defaults and Examples:
    4.45 -	  	     17 => 128 KB for S/390
    4.46 -		     16 => 64 KB for x86 NUMAQ or IA-64
    4.47 -	             15 => 32 KB for SMP
    4.48 -	             14 => 16 KB for uniprocessor
    4.49 -		     13 =>  8 KB
    4.50 -		     12 =>  4 KB
    4.51 -
    4.52 -config DETECT_SOFTLOCKUP
    4.53 -	bool "Detect Soft Lockups"
    4.54 -	depends on DEBUG_KERNEL
    4.55 -	default y
    4.56 -	help
    4.57 -	  Say Y here to enable the kernel to detect "soft lockups",
    4.58 -	  which are bugs that cause the kernel to loop in kernel
    4.59 -	  mode for more than 10 seconds, without giving other tasks a
    4.60 -	  chance to run.
    4.61 -
    4.62 -	  When a soft-lockup is detected, the kernel will print the
    4.63 -	  current stack trace (which you should report), but the
    4.64 -	  system will stay locked up. This feature has negligible
    4.65 -	  overhead.
    4.66 -
    4.67 -	  (Note that "hard lockups" are separate type of bugs that
    4.68 -	   can be detected via the NMI-watchdog, on platforms that
    4.69 -	   support it.)
    4.70 -
    4.71 -config SCHEDSTATS
    4.72 -	bool "Collect scheduler statistics"
    4.73 -	depends on DEBUG_KERNEL && PROC_FS
    4.74 -	help
    4.75 -	  If you say Y here, additional code will be inserted into the
    4.76 -	  scheduler and related routines to collect statistics about
    4.77 -	  scheduler behavior and provide them in /proc/schedstat.  These
    4.78 -	  stats may be useful for both tuning and debugging the scheduler
    4.79 -	  If you aren't debugging the scheduler or trying to tune a specific
    4.80 -	  application, you can say N to avoid the very slight overhead
    4.81 -	  this adds.
    4.82 -
    4.83 -config DEBUG_SLAB
    4.84 -	bool "Debug memory allocations"
    4.85 -	depends on DEBUG_KERNEL && SLAB
    4.86 -	help
    4.87 -	  Say Y here to have the kernel do limited verification on memory
    4.88 -	  allocation as well as poisoning memory on free to catch use of freed
    4.89 -	  memory. This can make kmalloc/kfree-intensive workloads much slower.
    4.90 -
    4.91 -config DEBUG_PREEMPT
    4.92 -	bool "Debug preemptible kernel"
    4.93 -	depends on DEBUG_KERNEL && PREEMPT
    4.94 -	default y
    4.95 -	help
    4.96 -	  If you say Y here then the kernel will use a debug variant of the
    4.97 -	  commonly used smp_processor_id() function and will print warnings
    4.98 -	  if kernel code uses it in a preemption-unsafe way. Also, the kernel
    4.99 -	  will detect preemption count underflows.
   4.100 -
   4.101 -config DEBUG_MUTEXES
   4.102 -	bool "Mutex debugging, deadlock detection"
   4.103 -	default y
   4.104 -	depends on DEBUG_KERNEL
   4.105 -	help
   4.106 -	 This allows mutex semantics violations and mutex related deadlocks
   4.107 -	 (lockups) to be detected and reported automatically.
   4.108 -
   4.109 -config DEBUG_SPINLOCK
   4.110 -	bool "Spinlock debugging"
   4.111 -	depends on DEBUG_KERNEL
   4.112 -	help
   4.113 -	  Say Y here and build SMP to catch missing spinlock initialization
   4.114 -	  and certain other kinds of spinlock errors commonly made.  This is
   4.115 -	  best used in conjunction with the NMI watchdog so that spinlock
   4.116 -	  deadlocks are also debuggable.
   4.117 -
   4.118 -config DEBUG_SPINLOCK_SLEEP
   4.119 -	bool "Sleep-inside-spinlock checking"
   4.120 -	depends on DEBUG_KERNEL
   4.121 -	help
   4.122 -	  If you say Y here, various routines which may sleep will become very
   4.123 -	  noisy if they are called with a spinlock held.
   4.124 -
   4.125 -config DEBUG_KOBJECT
   4.126 -	bool "kobject debugging"
   4.127 -	depends on DEBUG_KERNEL
   4.128 -	help
   4.129 -	  If you say Y here, some extra kobject debugging messages will be sent
   4.130 -	  to the syslog. 
   4.131 -
   4.132 -config DEBUG_HIGHMEM
   4.133 -	bool "Highmem debugging"
   4.134 -	depends on DEBUG_KERNEL && HIGHMEM
   4.135 -	help
   4.136 -	  This options enables addition error checking for high memory systems.
   4.137 -	  Disable for production systems.
   4.138 -
   4.139 -config DEBUG_BUGVERBOSE
   4.140 -	bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
   4.141 -	depends on BUG
   4.142 -	depends on ARM || ARM26 || M32R || M68K || SPARC32 || SPARC64 || X86_32 || FRV
   4.143 -	default !EMBEDDED
   4.144 -	help
   4.145 -	  Say Y here to make BUG() panics output the file name and line number
   4.146 -	  of the BUG call as well as the EIP and oops trace.  This aids
   4.147 -	  debugging but costs about 70-100K of memory.
   4.148 -
   4.149 -config DEBUG_INFO
   4.150 -	bool "Compile the kernel with debug info"
   4.151 -	depends on DEBUG_KERNEL && !X86_64_XEN
   4.152 -	help
   4.153 -          If you say Y here the resulting kernel image will include
   4.154 -	  debugging info resulting in a larger kernel image.
   4.155 -	  Say Y here only if you plan to debug the kernel.
   4.156 -
   4.157 -	  If unsure, say N.
   4.158 -
   4.159 -config DEBUG_IOREMAP
   4.160 -	bool "Enable ioremap() debugging"
   4.161 -	depends on DEBUG_KERNEL && PARISC
   4.162 -	help
   4.163 -	  Enabling this option will cause the kernel to distinguish between
   4.164 -	  ioremapped and physical addresses.  It will print a backtrace (at
   4.165 -	  most one every 10 seconds), hopefully allowing you to see which
   4.166 -	  drivers need work.  Fixing all these problems is a prerequisite
   4.167 -	  for turning on USE_HPPA_IOREMAP.  The warnings are harmless;
   4.168 -	  the kernel has enough information to fix the broken drivers
   4.169 -	  automatically, but we'd like to make it more efficient by not
   4.170 -	  having to do that.
   4.171 -
   4.172 -config DEBUG_FS
   4.173 -	bool "Debug Filesystem"
   4.174 -	depends on DEBUG_KERNEL && SYSFS
   4.175 -	help
   4.176 -	  debugfs is a virtual file system that kernel developers use to put
   4.177 -	  debugging files into.  Enable this option to be able to read and
   4.178 -	  write to these files.
   4.179 -
   4.180 -	  If unsure, say N.
   4.181 -
   4.182 -config DEBUG_VM
   4.183 -	bool "Debug VM"
   4.184 -	depends on DEBUG_KERNEL
   4.185 -	help
   4.186 -	  Enable this to turn on extended checks in the virtual-memory system
   4.187 -          that may impact performance.
   4.188 -
   4.189 -	  If unsure, say N.
   4.190 -
   4.191 -config FRAME_POINTER
   4.192 -	bool "Compile the kernel with frame pointers"
   4.193 -	depends on DEBUG_KERNEL && (X86 || CRIS || M68K || M68KNOMMU || FRV || UML)
   4.194 -	default y if DEBUG_INFO && UML
   4.195 -	help
   4.196 -	  If you say Y here the resulting kernel image will be slightly larger
   4.197 -	  and slower, but it might give very useful debugging information on
   4.198 -	  some architectures or if you use external debuggers.
   4.199 -	  If you don't debug the kernel, you can say N.
   4.200 -
   4.201 -config FORCED_INLINING
   4.202 -	bool "Force gcc to inline functions marked 'inline'"
   4.203 -	depends on DEBUG_KERNEL
   4.204 -	default y
   4.205 -	help
   4.206 -	  This option determines if the kernel forces gcc to inline the functions
   4.207 -	  developers have marked 'inline'. Doing so takes away freedom from gcc to
   4.208 -	  do what it thinks is best, which is desirable for the gcc 3.x series of
   4.209 -	  compilers. The gcc 4.x series have a rewritten inlining algorithm and
   4.210 -	  disabling this option will generate a smaller kernel there. Hopefully
   4.211 -	  this algorithm is so good that allowing gcc4 to make the decision can
   4.212 -	  become the default in the future, until then this option is there to
   4.213 -	  test gcc for this.
   4.214 -
   4.215 -config RCU_TORTURE_TEST
   4.216 -	tristate "torture tests for RCU"
   4.217 -	depends on DEBUG_KERNEL
   4.218 -	default n
   4.219 -	help
   4.220 -	  This option provides a kernel module that runs torture tests
   4.221 -	  on the RCU infrastructure.  The kernel module may be built
   4.222 -	  after the fact on the running kernel to be tested, if desired.
   4.223 -
   4.224 -	  Say Y here if you want RCU torture tests to start automatically
   4.225 -	  at boot time (you probably don't).
   4.226 -	  Say M if you want the RCU torture tests to build as a module.
   4.227 -	  Say N if you are unsure.