3 bool "Show timing information on printks"
5 Selecting this option causes timing information to be
6 included in printk output. This allows you to measure
7 the interval between kernel operations, including bootup
8 operations. This is useful for identifying long delays
13 bool "Kernel debugging"
15 Say Y here if you are developing drivers or trying to debug and
16 identify kernel problems.
19 bool "Magic SysRq key"
20 depends on DEBUG_KERNEL && !UML
22 If you say Y here, you will have some control over the system even
23 if the system crashes for example during kernel debugging (e.g., you
24 will be able to flush the buffer cache to disk, reboot the system
25 immediately or dump some status information). This is accomplished
26 by pressing various keys while holding SysRq (Alt+PrintScreen). It
27 also works on a serial console (on PC hardware at least), if you
28 send a BREAK and then within 5 seconds a command keypress. The
29 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
30 unless you really know what this hack does.
33 int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
36 default 16 if X86_NUMAQ || IA64
40 Select kernel log buffer size as a power of 2.
41 Defaults and Examples:
42 17 => 128 KB for S/390
43 16 => 64 KB for x86 NUMAQ or IA-64
45 14 => 16 KB for uniprocessor
49 config DETECT_SOFTLOCKUP
50 bool "Detect Soft Lockups"
51 depends on DEBUG_KERNEL
54 Say Y here to enable the kernel to detect "soft lockups",
55 which are bugs that cause the kernel to loop in kernel
56 mode for more than 10 seconds, without giving other tasks a
59 When a soft-lockup is detected, the kernel will print the
60 current stack trace (which you should report), but the
61 system will stay locked up. This feature has negligible
64 (Note that "hard lockups" are separate type of bugs that
65 can be detected via the NMI-watchdog, on platforms that
69 bool "Collect scheduler statistics"
70 depends on DEBUG_KERNEL && PROC_FS
72 If you say Y here, additional code will be inserted into the
73 scheduler and related routines to collect statistics about
74 scheduler behavior and provide them in /proc/schedstat. These
75 stats may be useful for both tuning and debugging the scheduler
76 If you aren't debugging the scheduler or trying to tune a specific
77 application, you can say N to avoid the very slight overhead
81 bool "Debug memory allocations"
82 depends on DEBUG_KERNEL && SLAB
84 Say Y here to have the kernel do limited verification on memory
85 allocation as well as poisoning memory on free to catch use of freed
86 memory. This can make kmalloc/kfree-intensive workloads much slower.
89 bool "Debug preemptible kernel"
90 depends on DEBUG_KERNEL && PREEMPT
93 If you say Y here then the kernel will use a debug variant of the
94 commonly used smp_processor_id() function and will print warnings
95 if kernel code uses it in a preemption-unsafe way. Also, the kernel
96 will detect preemption count underflows.
99 bool "Mutex debugging, deadlock detection"
101 depends on DEBUG_KERNEL
103 This allows mutex semantics violations and mutex related deadlocks
104 (lockups) to be detected and reported automatically.
106 config DEBUG_SPINLOCK
107 bool "Spinlock debugging"
108 depends on DEBUG_KERNEL
110 Say Y here and build SMP to catch missing spinlock initialization
111 and certain other kinds of spinlock errors commonly made. This is
112 best used in conjunction with the NMI watchdog so that spinlock
113 deadlocks are also debuggable.
115 config DEBUG_SPINLOCK_SLEEP
116 bool "Sleep-inside-spinlock checking"
117 depends on DEBUG_KERNEL
119 If you say Y here, various routines which may sleep will become very
120 noisy if they are called with a spinlock held.
123 bool "kobject debugging"
124 depends on DEBUG_KERNEL
126 If you say Y here, some extra kobject debugging messages will be sent
130 bool "Highmem debugging"
131 depends on DEBUG_KERNEL && HIGHMEM
133 This options enables addition error checking for high memory systems.
134 Disable for production systems.
136 config DEBUG_BUGVERBOSE
137 bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
139 depends on ARM || ARM26 || M32R || M68K || SPARC32 || SPARC64 || X86_32 || FRV
142 Say Y here to make BUG() panics output the file name and line number
143 of the BUG call as well as the EIP and oops trace. This aids
144 debugging but costs about 70-100K of memory.
147 bool "Compile the kernel with debug info"
148 depends on DEBUG_KERNEL
150 If you say Y here the resulting kernel image will include
151 debugging info resulting in a larger kernel image.
152 Say Y here only if you plan to debug the kernel.
157 bool "Enable ioremap() debugging"
158 depends on DEBUG_KERNEL && PARISC
160 Enabling this option will cause the kernel to distinguish between
161 ioremapped and physical addresses. It will print a backtrace (at
162 most one every 10 seconds), hopefully allowing you to see which
163 drivers need work. Fixing all these problems is a prerequisite
164 for turning on USE_HPPA_IOREMAP. The warnings are harmless;
165 the kernel has enough information to fix the broken drivers
166 automatically, but we'd like to make it more efficient by not
170 bool "Debug Filesystem"
171 depends on DEBUG_KERNEL && SYSFS
173 debugfs is a virtual file system that kernel developers use to put
174 debugging files into. Enable this option to be able to read and
175 write to these files.
181 depends on DEBUG_KERNEL
183 Enable this to turn on extended checks in the virtual-memory system
184 that may impact performance.
189 bool "Compile the kernel with frame pointers"
190 depends on DEBUG_KERNEL && (X86 || CRIS || M68K || M68KNOMMU || FRV || UML)
191 default y if DEBUG_INFO && UML
193 If you say Y here the resulting kernel image will be slightly larger
194 and slower, but it might give very useful debugging information on
195 some architectures or if you use external debuggers.
196 If you don't debug the kernel, you can say N.
198 config RCU_TORTURE_TEST
199 tristate "torture tests for RCU"
200 depends on DEBUG_KERNEL
203 This option provides a kernel module that runs torture tests
204 on the RCU infrastructure. The kernel module may be built
205 after the fact on the running kernel to be tested, if desired.
207 Say Y here if you want RCU torture tests to start automatically
208 at boot time (you probably don't).
209 Say M if you want the RCU torture tests to build as a module.
210 Say N if you are unsure.