3 source "lib/Kconfig.debug"
6 bool "Filter access to /dev/mem"
9 If this option is disabled, you allow userspace (root) access to all
10 of memory, including kernel and userspace memory. Accidental
11 access to this is obviously disastrous, but specific access can
12 be used by people debugging the kernel.
14 If this option is switched on, the /dev/mem file only allows
15 userspace access to memory mapped peripherals.
19 # RMK wants arm kernels compiled with frame pointers or stack unwinding.
20 # If you know what you are doing and are willing to live without stack
21 # traces, you can get a slightly smaller kernel by setting this option to
22 # n, but then RMK will have to kill you ;).
25 depends on !THUMB2_KERNEL
26 default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
28 If you say N here, the resulting kernel will be slightly smaller and
29 faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
30 when a problem occurs with the kernel, the information that is
31 reported is severely limited.
34 bool "Enable stack unwinding support (EXPERIMENTAL)"
35 depends on AEABI && EXPERIMENTAL
38 This option enables stack unwinding support in the kernel
39 using the information automatically generated by the
40 compiler. The resulting kernel image is slightly bigger but
41 the performance is not affected. Currently, this feature
42 only works with EABI compilers. If unsure say Y.
46 depends on FUNCTION_TRACER && FRAME_POINTER
50 bool "Verbose user fault messages"
52 When a user program crashes due to an exception, the kernel can
53 print a brief message explaining what the problem was. This is
54 sometimes helpful for debugging but serves no purpose on a
55 production system. Most people should say N here.
57 In addition, you need to pass user_debug=N on the kernel command
58 line to enable this feature. N consists of the sum of:
60 1 - undefined instruction events
62 4 - invalid data aborts
66 # These options are only for real kernel hackers who want to get their hands dirty.
68 bool "Kernel low-level debugging functions (read help!)"
69 depends on DEBUG_KERNEL
71 Say Y here to include definitions of printascii, printch, printhex
72 in the kernel. This is helpful if you are debugging code that
73 executes before the console is initialized.
75 Note that selecting this option will limit the kernel to a single
76 UART definition, as specified below. Attempting to boot the kernel
77 image on a different platform *will not work*, so this option should
78 not be enabled for kernels that are intended to be portable.
81 prompt "Kernel low-level debugging port"
84 config AT91_DEBUG_LL_DBGU0
85 bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
86 depends on HAVE_AT91_DBGU0
88 config AT91_DEBUG_LL_DBGU1
89 bool "Kernel low-level debugging on 9263 and 9g45"
90 depends on HAVE_AT91_DBGU1
92 config DEBUG_CLPS711X_UART1
93 bool "Kernel low-level debugging messages via UART1"
94 depends on ARCH_CLPS711X
96 Say Y here if you want the debug print routines to direct
97 their output to the first serial port on these devices.
99 config DEBUG_CLPS711X_UART2
100 bool "Kernel low-level debugging messages via UART2"
101 depends on ARCH_CLPS711X
103 Say Y here if you want the debug print routines to direct
104 their output to the second serial port on these devices.
106 config DEBUG_DAVINCI_DA8XX_UART1
107 bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
108 depends on ARCH_DAVINCI_DA8XX
110 Say Y here if you want the debug print routines to direct
111 their output to UART1 serial port on DaVinci DA8XX devices.
113 config DEBUG_DAVINCI_DA8XX_UART2
114 bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
115 depends on ARCH_DAVINCI_DA8XX
117 Say Y here if you want the debug print routines to direct
118 their output to UART2 serial port on DaVinci DA8XX devices.
120 config DEBUG_DAVINCI_DMx_UART0
121 bool "Kernel low-level debugging on DaVinci DMx using UART0"
122 depends on ARCH_DAVINCI_DMx
124 Say Y here if you want the debug print routines to direct
125 their output to UART0 serial port on DaVinci DMx devices.
127 config DEBUG_DAVINCI_TNETV107X_UART1
128 bool "Kernel low-level debugging on DaVinci TNETV107x using UART1"
129 depends on ARCH_DAVINCI_TNETV107X
131 Say Y here if you want the debug print routines to direct
132 their output to UART1 serial port on DaVinci TNETV107X
135 config DEBUG_DC21285_PORT
136 bool "Kernel low-level debugging messages via footbridge serial port"
137 depends on FOOTBRIDGE
139 Say Y here if you want the debug print routines to direct
140 their output to the serial port in the DC21285 (Footbridge).
142 config DEBUG_FOOTBRIDGE_COM1
143 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
144 depends on FOOTBRIDGE
146 Say Y here if you want the debug print routines to direct
147 their output to the 8250 at PCI COM1.
149 config DEBUG_HIGHBANK_UART
150 bool "Kernel low-level debugging messages via Highbank UART"
151 depends on ARCH_HIGHBANK
153 Say Y here if you want the debug print routines to direct
154 their output to the UART on Highbank based devices.
156 config DEBUG_IMX1_UART
157 bool "i.MX1 Debug UART"
160 Say Y here if you want kernel low-level debugging support
163 config DEBUG_IMX23_UART
164 bool "i.MX23 Debug UART"
167 Say Y here if you want kernel low-level debugging support
170 config DEBUG_IMX25_UART
171 bool "i.MX25 Debug UART"
174 Say Y here if you want kernel low-level debugging support
177 config DEBUG_IMX21_IMX27_UART
178 bool "i.MX21 and i.MX27 Debug UART"
179 depends on SOC_IMX21 || SOC_IMX27
181 Say Y here if you want kernel low-level debugging support
184 config DEBUG_IMX28_UART
185 bool "i.MX28 Debug UART"
188 Say Y here if you want kernel low-level debugging support
191 config DEBUG_IMX31_IMX35_UART
192 bool "i.MX31 and i.MX35 Debug UART"
193 depends on SOC_IMX31 || SOC_IMX35
195 Say Y here if you want kernel low-level debugging support
198 config DEBUG_IMX51_UART
199 bool "i.MX51 Debug UART"
202 Say Y here if you want kernel low-level debugging support
205 config DEBUG_IMX50_IMX53_UART
206 bool "i.MX50 and i.MX53 Debug UART"
207 depends on SOC_IMX50 || SOC_IMX53
209 Say Y here if you want kernel low-level debugging support
212 config DEBUG_IMX6Q_UART2
213 bool "i.MX6Q Debug UART2"
216 Say Y here if you want kernel low-level debugging support
217 on i.MX6Q UART2. This is correct for e.g. the SabreLite
220 config DEBUG_IMX6Q_UART4
221 bool "i.MX6Q Debug UART4"
224 Say Y here if you want kernel low-level debugging support
227 config DEBUG_MMP_UART2
228 bool "Kernel low-level debugging message via MMP UART2"
231 Say Y here if you want kernel low-level debugging support
234 config DEBUG_MMP_UART3
235 bool "Kernel low-level debugging message via MMP UART3"
238 Say Y here if you want kernel low-level debugging support
241 config DEBUG_MSM_UART1
242 bool "Kernel low-level debugging messages via MSM UART1"
243 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
245 Say Y here if you want the debug print routines to direct
246 their output to the first serial port on MSM devices.
248 config DEBUG_MSM_UART2
249 bool "Kernel low-level debugging messages via MSM UART2"
250 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
252 Say Y here if you want the debug print routines to direct
253 their output to the second serial port on MSM devices.
255 config DEBUG_MSM_UART3
256 bool "Kernel low-level debugging messages via MSM UART3"
257 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
259 Say Y here if you want the debug print routines to direct
260 their output to the third serial port on MSM devices.
262 config DEBUG_MSM8660_UART
263 bool "Kernel low-level debugging messages via MSM 8660 UART"
264 depends on ARCH_MSM8X60
265 select MSM_HAS_DEBUG_UART_HS
267 Say Y here if you want the debug print routines to direct
268 their output to the serial port on MSM 8660 devices.
270 config DEBUG_MSM8960_UART
271 bool "Kernel low-level debugging messages via MSM 8960 UART"
272 depends on ARCH_MSM8960
273 select MSM_HAS_DEBUG_UART_HS
275 Say Y here if you want the debug print routines to direct
276 their output to the serial port on MSM 8960 devices.
278 config DEBUG_REALVIEW_STD_PORT
279 bool "RealView Default UART"
280 depends on ARCH_REALVIEW
282 Say Y here if you want the debug print routines to direct
283 their output to the serial port on RealView EB, PB11MP, PBA8
286 config DEBUG_REALVIEW_PB1176_PORT
287 bool "RealView PB1176 UART"
288 depends on MACH_REALVIEW_PB1176
290 Say Y here if you want the debug print routines to direct
291 their output to the standard serial port on the RealView
294 config DEBUG_S3C_UART0
295 depends on PLAT_SAMSUNG
296 bool "Use S3C UART 0 for low-level debug"
298 Say Y here if you want the debug print routines to direct
299 their output to UART 0. The port must have been initialised
300 by the boot-loader before use.
302 The uncompressor code port configuration is now handled
303 by CONFIG_S3C_LOWLEVEL_UART_PORT.
305 config DEBUG_S3C_UART1
306 depends on PLAT_SAMSUNG
307 bool "Use S3C UART 1 for low-level debug"
309 Say Y here if you want the debug print routines to direct
310 their output to UART 1. The port must have been initialised
311 by the boot-loader before use.
313 The uncompressor code port configuration is now handled
314 by CONFIG_S3C_LOWLEVEL_UART_PORT.
316 config DEBUG_S3C_UART2
317 depends on PLAT_SAMSUNG
318 bool "Use S3C UART 2 for low-level debug"
320 Say Y here if you want the debug print routines to direct
321 their output to UART 2. The port must have been initialised
322 by the boot-loader before use.
324 The uncompressor code port configuration is now handled
325 by CONFIG_S3C_LOWLEVEL_UART_PORT.
327 config DEBUG_VEXPRESS_UART0_DETECT
328 bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
329 depends on ARCH_VEXPRESS && CPU_CP15_MMU
331 This option enables a simple heuristic which tries to determine
332 the motherboard's memory map variant (original or RS1) and then
333 choose the relevant UART0 base address.
335 Note that this will only work with standard A-class core tiles,
336 and may fail with non-standard SMM or custom software models.
338 config DEBUG_VEXPRESS_UART0_CA9
339 bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
340 depends on ARCH_VEXPRESS
342 This option selects UART0 at 0x10009000. Except for custom models,
343 this applies only to the V2P-CA9 tile.
345 config DEBUG_VEXPRESS_UART0_RS1
346 bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
347 depends on ARCH_VEXPRESS
349 This option selects UART0 at 0x1c090000. This applies to most
350 of the tiles using the RS1 memory map, including all new A-class
351 core tiles, FPGA-based SMMs and software models.
353 config DEBUG_LL_UART_NONE
354 bool "No low-level debugging UART"
356 Say Y here if your platform doesn't provide a UART option
357 below. This relies on your platform choosing the right UART
358 definition internally in order for low-level debugging to
362 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
364 Say Y here if you want the debug print routines to direct
365 their output to the EmbeddedICE macrocell's DCC channel using
366 co-processor 14. This is known to work on the ARM9 style ICE
367 channel and on the XScale with the PEEDI.
369 Note that the system will appear to hang during boot if there
370 is nothing connected to read from the DCC.
372 config DEBUG_SEMIHOSTING
373 bool "Kernel low-level debug output via semihosting I/O"
375 Semihosting enables code running on an ARM target to use
376 the I/O facilities on a host debugger/emulator through a
377 simple SVC call. The host debugger or emulator must have
378 semihosting enabled for the special svc call to be trapped
379 otherwise the kernel will crash.
381 This is known to work with OpenOCD, as well as
382 ARM's Fast Models, or any other controlling environment
383 that implements semihosting.
385 For more details about semihosting, please see
386 chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
394 Say Y here if you want to have an early console using the
395 kernel low-level debugging functions. Add earlyprintk to your
396 kernel parameters to enable this console.
399 bool "On-chip ETM and ETB"
402 Enables the on-chip embedded trace macrocell and embedded trace
403 buffer driver that will allow you to collect traces of the
406 config ARM_KPROBES_TEST
407 tristate "Kprobes test module"
408 depends on KPROBES && MODULES
410 Perform tests of kprobes API and instruction set simulation.
412 config PID_IN_CONTEXTIDR
413 bool "Write the current PID to the CONTEXTIDR register"
414 depends on CPU_COPY_V6
416 Enabling this option causes the kernel to write the current PID to
417 the PROCID field of the CONTEXTIDR register, at the expense of some
418 additional instructions during context switch. Say Y here only if you
419 are planning to use hardware trace tools with this kernel.