Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Kernel hacking" |
2 | ||
55f327fa | 3 | config TRACE_IRQFLAGS_SUPPORT |
d013a27c | 4 | def_bool y |
55f327fa | 5 | |
1da177e4 LT |
6 | source "lib/Kconfig.debug" |
7 | ||
64d206d8 IM |
8 | config PROMISC_DEVMEM |
9 | bool "Allow unlimited access to /dev/mem" | |
10 | default y | |
ae531c26 | 11 | help |
64d206d8 | 12 | If this option is left on, you allow userspace (root) access to all |
16104b55 SR |
13 | of memory, including kernel and userspace memory. Accidental |
14 | access to this is obviously disastrous, but specific access can | |
15 | be used by people debugging the kernel. | |
16 | ||
17 | If this option is switched on, the /dev/mem file only allows | |
18 | userspace access to PCI space and the BIOS code and data regions. | |
19 | This is sufficient for dosemu and X and all common users of | |
20 | /dev/mem. | |
21 | ||
22 | If in doubt, say Y. | |
ae531c26 | 23 | |
6bcb13b3 BC |
24 | config X86_VERBOSE_BOOTUP |
25 | bool "Enable verbose x86 bootup info messages" | |
26 | default y | |
27 | help | |
28 | Enables the informational output from the decompression stage | |
29 | (e.g. bzImage) of the boot. If you disable this you will still | |
30 | see errors. Disable this if you want silent bootup. | |
31 | ||
1da177e4 | 32 | config EARLY_PRINTK |
076f9776 | 33 | bool "Early printk" if EMBEDDED |
1da177e4 LT |
34 | default y |
35 | help | |
36 | Write kernel log output directly into the VGA buffer or to a serial | |
37 | port. | |
38 | ||
39 | This is useful for kernel debugging when your machine crashes very | |
40 | early before the console code is initialized. For normal operation | |
41 | it is not recommended because it looks ugly and doesn't cooperate | |
42 | with klogd/syslogd or the X server. You should normally N here, | |
43 | unless you want to debug such a crash. | |
44 | ||
45 | config DEBUG_STACKOVERFLOW | |
46 | bool "Check for stack overflows" | |
47 | depends on DEBUG_KERNEL | |
dab175f3 AB |
48 | help |
49 | This option will cause messages to be printed if free stack space | |
50 | drops below a certain limit. | |
1da177e4 | 51 | |
1da177e4 LT |
52 | config DEBUG_STACK_USAGE |
53 | bool "Stack utilization instrumentation" | |
54 | depends on DEBUG_KERNEL | |
55 | help | |
56 | Enables the display of the minimum amount of free stack which each | |
57 | task has ever had available in the sysrq-T and sysrq-P debug output. | |
58 | ||
59 | This option will slow down process creation somewhat. | |
60 | ||
1da177e4 | 61 | config DEBUG_PAGEALLOC |
4a2f0acf | 62 | bool "Debug page memory allocations" |
b1d95f4e | 63 | depends on DEBUG_KERNEL |
1da177e4 LT |
64 | help |
65 | Unmap pages from the kernel linear mapping after free_pages(). | |
66 | This results in a large slowdown, but helps to find certain types | |
67 | of memory corruptions. | |
68 | ||
c49a4955 | 69 | config DEBUG_PER_CPU_MAPS |
70 | bool "Debug access to per_cpu maps" | |
71 | depends on DEBUG_KERNEL | |
23ca4bba | 72 | depends on X86_SMP |
c49a4955 | 73 | default n |
74 | help | |
75 | Say Y to verify that the per_cpu map being accessed has | |
76 | been setup. Adds a fair amount of code to kernel memory | |
77 | and decreases performance. | |
78 | ||
79 | Say N if unsure. | |
80 | ||
926e5392 AV |
81 | config X86_PTDUMP |
82 | bool "Export kernel pagetable layout to userspace via debugfs" | |
fe770bf0 | 83 | depends on DEBUG_KERNEL |
926e5392 AV |
84 | select DEBUG_FS |
85 | help | |
86 | Say Y here if you want to show the kernel pagetable layout in a | |
87 | debugfs file. This information is only useful for kernel developers | |
88 | who are working in architecture specific areas of the kernel. | |
89 | It is probably not a good idea to enable this feature in a production | |
90 | kernel. | |
91 | If in doubt, say "N" | |
92 | ||
63aaf308 AV |
93 | config DEBUG_RODATA |
94 | bool "Write protect kernel read-only data structures" | |
11201e60 | 95 | default y |
63aaf308 AV |
96 | depends on DEBUG_KERNEL |
97 | help | |
98 | Mark the kernel read-only data as write-protected in the pagetables, | |
99 | in order to catch accidental (and incorrect) writes to such const | |
11201e60 IM |
100 | data. This is recommended so that we can catch kernel bugs sooner. |
101 | If in doubt, say "Y". | |
63aaf308 | 102 | |
00d1c5e0 IM |
103 | config DIRECT_GBPAGES |
104 | bool "Enable gbpages-mapped kernel pagetables" | |
105 | depends on DEBUG_KERNEL && EXPERIMENTAL && X86_64 | |
106 | help | |
107 | Enable gigabyte pages support (if the CPU supports it). This can | |
108 | improve the kernel's performance a tiny bit by reducing TLB | |
109 | pressure. | |
110 | ||
111 | This is experimental code. | |
112 | ||
113 | If in doubt, say "N". | |
114 | ||
aba8391f IM |
115 | config DEBUG_RODATA_TEST |
116 | bool "Testcase for the DEBUG_RODATA feature" | |
117 | depends on DEBUG_RODATA | |
118 | help | |
119 | This option enables a testcase for the DEBUG_RODATA | |
120 | feature as well as for the change_page_attr() infrastructure. | |
121 | If in doubt, say "N" | |
122 | ||
123 | config DEBUG_NX_TEST | |
124 | tristate "Testcase for the NX non-executable stack feature" | |
125 | depends on DEBUG_KERNEL && m | |
126 | help | |
127 | This option enables a testcase for the CPU NX capability | |
128 | and the software setup of this feature. | |
129 | If in doubt, say "N" | |
130 | ||
1da177e4 LT |
131 | config 4KSTACKS |
132 | bool "Use 4Kb for kernel stacks instead of 8Kb" | |
d013a27c | 133 | depends on X86_32 |
1da177e4 LT |
134 | help |
135 | If you say Y here the kernel will use a 4Kb stacksize for the | |
136 | kernel stack attached to each process/thread. This facilitates | |
137 | running more threads on a system and also reduces the pressure | |
138 | on the VM subsystem for higher order allocations. This option | |
139 | will also use IRQ stacks to compensate for the reduced stackspace. | |
140 | ||
102e41fd AK |
141 | config DOUBLEFAULT |
142 | default y | |
143 | bool "Enable doublefault exception handler" if EMBEDDED | |
d013a27c RD |
144 | depends on X86_32 |
145 | help | |
146 | This option allows trapping of rare doublefault exceptions that | |
147 | would otherwise cause a system to silently reboot. Disabling this | |
148 | option saves about 4k and might cause you much additional grey | |
149 | hair. | |
150 | ||
151 | config IOMMU_DEBUG | |
152 | bool "Enable IOMMU debugging" | |
966396d3 | 153 | depends on GART_IOMMU && DEBUG_KERNEL |
d013a27c | 154 | depends on X86_64 |
102e41fd | 155 | help |
d013a27c RD |
156 | Force the IOMMU to on even when you have less than 4GB of |
157 | memory and add debugging code. On overflow always panic. And | |
158 | allow to enable IOMMU leak tracing. Can be disabled at boot | |
159 | time with iommu=noforce. This will also enable scatter gather | |
160 | list merging. Currently not recommended for production | |
161 | code. When you use it make sure you have a big enough | |
162 | IOMMU/AGP aperture. Most of the options enabled by this can | |
163 | be set more finegrained using the iommu= command line | |
164 | options. See Documentation/x86_64/boot-options.txt for more | |
165 | details. | |
166 | ||
167 | config IOMMU_LEAK | |
168 | bool "IOMMU leak tracing" | |
169 | depends on DEBUG_KERNEL | |
170 | depends on IOMMU_DEBUG | |
171 | help | |
172 | Add a simple leak tracer to the IOMMU code. This is useful when you | |
173 | are debugging a buggy device driver that leaks IOMMU mappings. | |
174 | ||
10c43d2e PP |
175 | config MMIOTRACE_HOOKS |
176 | bool | |
86069782 | 177 | |
8b7d89d0 | 178 | config MMIOTRACE |
d61fc448 | 179 | bool "Memory mapped IO tracing" |
37b36192 | 180 | depends on DEBUG_KERNEL && PCI |
f984b51e | 181 | select TRACING |
10c43d2e | 182 | select MMIOTRACE_HOOKS |
8b7d89d0 | 183 | help |
d61fc448 PP |
184 | Mmiotrace traces Memory Mapped I/O access and is meant for |
185 | debugging and reverse engineering. It is called from the ioremap | |
c6c67c1a | 186 | implementation and works via page faults. Tracing is disabled by |
37b36192 | 187 | default and can be enabled at run-time. |
8b7d89d0 | 188 | |
c6c67c1a | 189 | See Documentation/tracers/mmiotrace.txt. |
8b7d89d0 PP |
190 | If you are not helping to develop drivers, say N. |
191 | ||
192 | config MMIOTRACE_TEST | |
193 | tristate "Test module for mmiotrace" | |
194 | depends on MMIOTRACE && m | |
8b7d89d0 PP |
195 | help |
196 | This is a dumb module for testing mmiotrace. It is very dangerous | |
197 | as it will write garbage to IO memory starting at a given address. | |
198 | However, it should be safe to use on e.g. unused portion of VRAM. | |
199 | ||
200 | Say N, unless you absolutely know what you are doing. | |
201 | ||
6e7c4025 IM |
202 | # |
203 | # IO delay types: | |
204 | # | |
205 | ||
206 | config IO_DELAY_TYPE_0X80 | |
207 | int | |
208 | default "0" | |
209 | ||
210 | config IO_DELAY_TYPE_0XED | |
211 | int | |
212 | default "1" | |
213 | ||
214 | config IO_DELAY_TYPE_UDELAY | |
215 | int | |
216 | default "2" | |
217 | ||
218 | config IO_DELAY_TYPE_NONE | |
219 | int | |
220 | default "3" | |
221 | ||
222 | choice | |
223 | prompt "IO delay type" | |
fd59e9e9 | 224 | default IO_DELAY_0X80 |
6e7c4025 IM |
225 | |
226 | config IO_DELAY_0X80 | |
227 | bool "port 0x80 based port-IO delay [recommended]" | |
228 | help | |
229 | This is the traditional Linux IO delay used for in/out_p. | |
230 | It is the most tested hence safest selection here. | |
231 | ||
232 | config IO_DELAY_0XED | |
233 | bool "port 0xed based port-IO delay" | |
234 | help | |
235 | Use port 0xed as the IO delay. This frees up port 0x80 which is | |
236 | often used as a hardware-debug port. | |
237 | ||
238 | config IO_DELAY_UDELAY | |
239 | bool "udelay based port-IO delay" | |
240 | help | |
241 | Use udelay(2) as the IO delay method. This provides the delay | |
242 | while not having any side-effect on the IO port space. | |
243 | ||
244 | config IO_DELAY_NONE | |
245 | bool "no port-IO delay" | |
b02aae9c | 246 | help |
6e7c4025 IM |
247 | No port-IO delay. Will break on old boxes that require port-IO |
248 | delay for certain operations. Should work on most new machines. | |
249 | ||
250 | endchoice | |
251 | ||
252 | if IO_DELAY_0X80 | |
253 | config DEFAULT_IO_DELAY_TYPE | |
254 | int | |
255 | default IO_DELAY_TYPE_0X80 | |
256 | endif | |
257 | ||
258 | if IO_DELAY_0XED | |
259 | config DEFAULT_IO_DELAY_TYPE | |
260 | int | |
261 | default IO_DELAY_TYPE_0XED | |
262 | endif | |
263 | ||
264 | if IO_DELAY_UDELAY | |
265 | config DEFAULT_IO_DELAY_TYPE | |
266 | int | |
267 | default IO_DELAY_TYPE_UDELAY | |
268 | endif | |
269 | ||
270 | if IO_DELAY_NONE | |
271 | config DEFAULT_IO_DELAY_TYPE | |
272 | int | |
273 | default IO_DELAY_TYPE_NONE | |
274 | endif | |
b02aae9c | 275 | |
6d7d7433 HY |
276 | config DEBUG_BOOT_PARAMS |
277 | bool "Debug boot parameters" | |
278 | depends on DEBUG_KERNEL | |
279 | depends on DEBUG_FS | |
280 | help | |
281 | This option will cause struct boot_params to be exported via debugfs. | |
282 | ||
0c42f392 | 283 | config CPA_DEBUG |
971a52d6 | 284 | bool "CPA self-test code" |
f316fe68 | 285 | depends on DEBUG_KERNEL |
0c42f392 | 286 | help |
971a52d6 | 287 | Do change_page_attr() self-tests every 30 seconds. |
0c42f392 | 288 | |
60a3cdd0 IM |
289 | config OPTIMIZE_INLINING |
290 | bool "Allow gcc to uninline functions marked 'inline'" | |
6d98ca73 | 291 | depends on BROKEN |
60a3cdd0 IM |
292 | help |
293 | This option determines if the kernel forces gcc to inline the functions | |
294 | developers have marked 'inline'. Doing so takes away freedom from gcc to | |
295 | do what it thinks is best, which is desirable for the gcc 3.x series of | |
296 | compilers. The gcc 4.x series have a rewritten inlining algorithm and | |
297 | disabling this option will generate a smaller kernel there. Hopefully | |
298 | this algorithm is so good that allowing gcc4 to make the decision can | |
299 | become the default in the future, until then this option is there to | |
300 | test gcc for this. | |
c9af1e33 IM |
301 | |
302 | endmenu | |
303 |