3 source "lib/Kconfig.debug"
6 tristate "Crash dump support (EXPERIMENTAL)"
7 depends on EXPERIMENTAL
10 Say Y here to enable saving an image of system memory when a panic
11 or other error occurs. Dumps can also be forced with the SysRq+d
12 key if MAGIC_SYSRQ is enabled.
14 config CRASH_DUMP_BLOCKDEV
15 tristate "Crash dump block device driver"
18 Say Y to allow saving crash dumps directly to a disk device.
20 config CRASH_DUMP_NETDEV
21 tristate "Crash dump network device driver"
24 Say Y to allow saving crash dumps over a network device.
26 config CRASH_DUMP_MEMDEV
27 bool "Crash dump staged memory driver"
30 Say Y to allow intermediate saving crash dumps in spare
31 memory pages which would then be written out to disk
34 config CRASH_DUMP_SOFTBOOT
35 bool "Save crash dump across a soft reboot"
36 depends on CRASH_DUMP_MEMDEV
38 Say Y to allow a crash dump to be preserved in memory
39 pages across a soft reboot and written out to disk
40 thereafter. For this to work, CRASH_DUMP must be
41 configured as part of the kernel (not as a module).
43 config CRASH_DUMP_COMPRESS_RLE
44 tristate "Crash dump RLE compression"
47 Say Y to allow saving dumps with Run Length Encoding compression.
49 config CRASH_DUMP_COMPRESS_GZIP
50 tristate "Crash dump GZIP compression"
55 Say Y to allow saving dumps with Gnu Zip compression.
57 config X86_FIND_SMP_CONFIG
59 depends on X86_LOCAL_APIC || X86_VOYAGER
64 depends on X86_LOCAL_APIC && !X86_VISWS
68 bool "Early printk" if EMBEDDED
71 Write kernel log output directly into the VGA buffer or to a serial
74 This is useful for kernel debugging when your machine crashes very
75 early before the console code is initialized. For normal operation
76 it is not recommended because it looks ugly and doesn't cooperate
77 with klogd/syslogd or the X server. You should normally N here,
78 unless you want to debug such a crash.
82 depends on DEBUG_KERNEL
84 Kprobes allows you to trap at almost any kernel address and
85 execute a callback function. register_kprobe() establishes
86 a probepoint and specifies the callback. Kprobes is useful
87 for kernel debugging, non-intrusive instrumentation and testing.
90 config DEBUG_PAGEALLOC
91 bool "Page alloc debugging"
92 depends on DEBUG_KERNEL
94 Unmap pages from the kernel linear mapping after free_pages().
95 This results in a large slowdown, but helps to find certain types
96 of memory corruptions.
98 config DEBUG_STACKOVERFLOW
99 bool "Check for stack overflows"
100 depends on DEBUG_KERNEL
102 config DEBUG_STACK_USAGE
103 bool "Stack utilization instrumentation"
104 depends on DEBUG_KERNEL
106 Enables the display of the minimum amount of free stack which each
107 task has ever had available in the sysrq-T and sysrq-P debug output.
109 This option will slow down process creation somewhat.
112 bool "Use separate IRQ stacks"
114 This option subsumes the IRQ stack implementation of the orig. 4KSTACK
115 support. You must use this if you select 4KB stacks!
117 config STACK_SIZE_SHIFT
118 int "Kernel stack size (12 => 4KB, 13 => 8KB, 14 => 16KB)"
120 default 12 if IRQSTACKS
123 Select kernel stack size. 4KB stacks are best as they let
124 the system scale further. Use 8KB stacks if you have an
125 experimental kernel where a stack overlow with a 4KB stack
126 might occur. Use 16KB stacks if you want to safely support
127 Windows device drivers using either Linuxant or ndiswrapper.
130 int "Print stack trace when stack grows beyond specified bytes"
131 default 4096 if IRQSTACKS
134 The kernel will print a stack trace when the current stack exceeds
137 config X86_STACK_CHECK
138 bool "Aggressively check for stack overflows"
141 Say Y here to have the kernel attempt to detect when the per-task
142 kernel stack overflows.
144 Some older versions of gcc don't handle the -p option correctly.
145 Kernprof is affected by the same problem, which is described here:
146 http://oss.sgi.com/projects/kernprof/faq.html#Q9
148 Basically, if you get oopses in __free_pages_ok during boot when
149 you have this turned on, you need to fix gcc. The Redhat 2.96
150 version and gcc-3.x seem to work.
152 If not debugging a stack overflow problem, say N
155 int "Panic when stack approaches with specified bytes of the stack limit"
156 depends on X86_STACK_CHECK
157 default 512 if IRQSTACKS
160 Panic if the stack grows to within specified byte range.
162 config DEBUG_PAGEALLOC
163 bool "Page alloc debugging"
164 depends on DEBUG_KERNEL
166 Unmap pages from the kernel linear mapping after free_pages().
167 This results in a large slowdown, but helps to find certain types
168 of memory corruptions.
171 bool "Collect scheduler statistics"
172 depends on DEBUG_KERNEL && PROC_FS
174 If you say Y here, additional code will be inserted into the
175 scheduler and related routines to collect statistics about
176 scheduler behavior and provide them in /proc/schedstat. These
177 stats may be useful for both tuning and debugging the scheduler
178 If you aren't debugging the scheduler or trying to tune a specific
179 application, you can say N to avoid the very slight overhead
182 config X86_FIND_SMP_CONFIG
184 depends on X86_LOCAL_APIC || X86_VOYAGER
189 depends on X86_LOCAL_APIC && !X86_VISWS