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_ZYNQ_UART0
136 bool "Kernel low-level debugging on Xilinx Zynq using UART0"
139 Say Y here if you want the debug print routines to direct
140 their output to UART0 on the Zynq platform.
142 config DEBUG_ZYNQ_UART1
143 bool "Kernel low-level debugging on Xilinx Zynq using UART1"
146 Say Y here if you want the debug print routines to direct
147 their output to UART1 on the Zynq platform.
149 If you have a ZC702 board and want early boot messages to
150 appear on the USB serial adaptor, select this option.
152 config DEBUG_DC21285_PORT
153 bool "Kernel low-level debugging messages via footbridge serial port"
154 depends on FOOTBRIDGE
156 Say Y here if you want the debug print routines to direct
157 their output to the serial port in the DC21285 (Footbridge).
159 config DEBUG_FOOTBRIDGE_COM1
160 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
161 depends on FOOTBRIDGE
163 Say Y here if you want the debug print routines to direct
164 their output to the 8250 at PCI COM1.
166 config DEBUG_HIGHBANK_UART
167 bool "Kernel low-level debugging messages via Highbank UART"
168 depends on ARCH_HIGHBANK
170 Say Y here if you want the debug print routines to direct
171 their output to the UART on Highbank based devices.
173 config DEBUG_IMX1_UART
174 bool "i.MX1 Debug UART"
177 Say Y here if you want kernel low-level debugging support
180 config DEBUG_IMX23_UART
181 bool "i.MX23 Debug UART"
184 Say Y here if you want kernel low-level debugging support
187 config DEBUG_IMX25_UART
188 bool "i.MX25 Debug UART"
191 Say Y here if you want kernel low-level debugging support
194 config DEBUG_IMX21_IMX27_UART
195 bool "i.MX21 and i.MX27 Debug UART"
196 depends on SOC_IMX21 || SOC_IMX27
198 Say Y here if you want kernel low-level debugging support
201 config DEBUG_IMX28_UART
202 bool "i.MX28 Debug UART"
205 Say Y here if you want kernel low-level debugging support
208 config DEBUG_IMX31_IMX35_UART
209 bool "i.MX31 and i.MX35 Debug UART"
210 depends on SOC_IMX31 || SOC_IMX35
212 Say Y here if you want kernel low-level debugging support
215 config DEBUG_IMX51_UART
216 bool "i.MX51 Debug UART"
219 Say Y here if you want kernel low-level debugging support
222 config DEBUG_IMX50_IMX53_UART
223 bool "i.MX50 and i.MX53 Debug UART"
224 depends on SOC_IMX50 || SOC_IMX53
226 Say Y here if you want kernel low-level debugging support
229 config DEBUG_IMX6Q_UART2
230 bool "i.MX6Q Debug UART2"
233 Say Y here if you want kernel low-level debugging support
234 on i.MX6Q UART2. This is correct for e.g. the SabreLite
237 config DEBUG_IMX6Q_UART4
238 bool "i.MX6Q Debug UART4"
241 Say Y here if you want kernel low-level debugging support
244 config DEBUG_MMP_UART2
245 bool "Kernel low-level debugging message via MMP UART2"
248 Say Y here if you want kernel low-level debugging support
251 config DEBUG_MMP_UART3
252 bool "Kernel low-level debugging message via MMP UART3"
255 Say Y here if you want kernel low-level debugging support
258 config DEBUG_MSM_UART1
259 bool "Kernel low-level debugging messages via MSM UART1"
260 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
262 Say Y here if you want the debug print routines to direct
263 their output to the first serial port on MSM devices.
265 config DEBUG_MSM_UART2
266 bool "Kernel low-level debugging messages via MSM UART2"
267 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
269 Say Y here if you want the debug print routines to direct
270 their output to the second serial port on MSM devices.
272 config DEBUG_MSM_UART3
273 bool "Kernel low-level debugging messages via MSM UART3"
274 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
276 Say Y here if you want the debug print routines to direct
277 their output to the third serial port on MSM devices.
279 config DEBUG_MSM8660_UART
280 bool "Kernel low-level debugging messages via MSM 8660 UART"
281 depends on ARCH_MSM8X60
282 select MSM_HAS_DEBUG_UART_HS
284 Say Y here if you want the debug print routines to direct
285 their output to the serial port on MSM 8660 devices.
287 config DEBUG_MSM8960_UART
288 bool "Kernel low-level debugging messages via MSM 8960 UART"
289 depends on ARCH_MSM8960
290 select MSM_HAS_DEBUG_UART_HS
292 Say Y here if you want the debug print routines to direct
293 their output to the serial port on MSM 8960 devices.
295 config DEBUG_MVEBU_UART
296 bool "Kernel low-level debugging messages via MVEBU UART"
297 depends on ARCH_MVEBU
299 Say Y here if you want kernel low-level debugging support
300 on MVEBU based platforms.
302 config DEBUG_PICOXCELL_UART
303 depends on ARCH_PICOXCELL
304 bool "Use PicoXcell UART for low-level debug"
306 Say Y here if you want kernel low-level debugging support
307 on PicoXcell based platforms.
309 config DEBUG_REALVIEW_STD_PORT
310 bool "RealView Default UART"
311 depends on ARCH_REALVIEW
313 Say Y here if you want the debug print routines to direct
314 their output to the serial port on RealView EB, PB11MP, PBA8
317 config DEBUG_REALVIEW_PB1176_PORT
318 bool "RealView PB1176 UART"
319 depends on MACH_REALVIEW_PB1176
321 Say Y here if you want the debug print routines to direct
322 their output to the standard serial port on the RealView
325 config DEBUG_S3C_UART0
326 depends on PLAT_SAMSUNG
327 bool "Use S3C UART 0 for low-level debug"
329 Say Y here if you want the debug print routines to direct
330 their output to UART 0. The port must have been initialised
331 by the boot-loader before use.
333 The uncompressor code port configuration is now handled
334 by CONFIG_S3C_LOWLEVEL_UART_PORT.
336 config DEBUG_S3C_UART1
337 depends on PLAT_SAMSUNG
338 bool "Use S3C UART 1 for low-level debug"
340 Say Y here if you want the debug print routines to direct
341 their output to UART 1. The port must have been initialised
342 by the boot-loader before use.
344 The uncompressor code port configuration is now handled
345 by CONFIG_S3C_LOWLEVEL_UART_PORT.
347 config DEBUG_S3C_UART2
348 depends on PLAT_SAMSUNG
349 bool "Use S3C UART 2 for low-level debug"
351 Say Y here if you want the debug print routines to direct
352 their output to UART 2. The port must have been initialised
353 by the boot-loader before use.
355 The uncompressor code port configuration is now handled
356 by CONFIG_S3C_LOWLEVEL_UART_PORT.
358 config DEBUG_SOCFPGA_UART
359 depends on ARCH_SOCFPGA
360 bool "Use SOCFPGA UART for low-level debug"
362 Say Y here if you want kernel low-level debugging support
363 on SOCFPGA based platforms.
365 config DEBUG_VEXPRESS_UART0_DETECT
366 bool "Autodetect UART0 on Versatile Express Cortex-A core tiles"
367 depends on ARCH_VEXPRESS && CPU_CP15_MMU
369 This option enables a simple heuristic which tries to determine
370 the motherboard's memory map variant (original or RS1) and then
371 choose the relevant UART0 base address.
373 Note that this will only work with standard A-class core tiles,
374 and may fail with non-standard SMM or custom software models.
376 config DEBUG_VEXPRESS_UART0_CA9
377 bool "Use PL011 UART0 at 0x10009000 (V2P-CA9 core tile)"
378 depends on ARCH_VEXPRESS
380 This option selects UART0 at 0x10009000. Except for custom models,
381 this applies only to the V2P-CA9 tile.
383 config DEBUG_VEXPRESS_UART0_RS1
384 bool "Use PL011 UART0 at 0x1c090000 (RS1 complaint tiles)"
385 depends on ARCH_VEXPRESS
387 This option selects UART0 at 0x1c090000. This applies to most
388 of the tiles using the RS1 memory map, including all new A-class
389 core tiles, FPGA-based SMMs and software models.
391 config DEBUG_LL_UART_NONE
392 bool "No low-level debugging UART"
393 depends on !ARCH_MULTIPLATFORM
395 Say Y here if your platform doesn't provide a UART option
396 below. This relies on your platform choosing the right UART
397 definition internally in order for low-level debugging to
401 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
403 Say Y here if you want the debug print routines to direct
404 their output to the EmbeddedICE macrocell's DCC channel using
405 co-processor 14. This is known to work on the ARM9 style ICE
406 channel and on the XScale with the PEEDI.
408 Note that the system will appear to hang during boot if there
409 is nothing connected to read from the DCC.
411 config DEBUG_SEMIHOSTING
412 bool "Kernel low-level debug output via semihosting I/O"
414 Semihosting enables code running on an ARM target to use
415 the I/O facilities on a host debugger/emulator through a
416 simple SVC call. The host debugger or emulator must have
417 semihosting enabled for the special svc call to be trapped
418 otherwise the kernel will crash.
420 This is known to work with OpenOCD, as well as
421 ARM's Fast Models, or any other controlling environment
422 that implements semihosting.
424 For more details about semihosting, please see
425 chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
429 config DEBUG_LL_INCLUDE
431 default "debug/icedcc.S" if DEBUG_ICEDCC
432 default "debug/highbank.S" if DEBUG_HIGHBANK_UART
433 default "debug/mvebu.S" if DEBUG_MVEBU_UART
434 default "debug/picoxcell.S" if DEBUG_PICOXCELL_UART
435 default "debug/socfpga.S" if DEBUG_SOCFPGA_UART
436 default "debug/vexpress.S" if DEBUG_VEXPRESS_UART0_DETECT || \
437 DEBUG_VEXPRESS_UART0_CA9 || DEBUG_VEXPRESS_UART0_RS1
438 default "mach/debug-macro.S"
444 Say Y here if you want to have an early console using the
445 kernel low-level debugging functions. Add earlyprintk to your
446 kernel parameters to enable this console.
449 bool "On-chip ETM and ETB"
452 Enables the on-chip embedded trace macrocell and embedded trace
453 buffer driver that will allow you to collect traces of the
456 config ARM_KPROBES_TEST
457 tristate "Kprobes test module"
458 depends on KPROBES && MODULES
460 Perform tests of kprobes API and instruction set simulation.
462 config PID_IN_CONTEXTIDR
463 bool "Write the current PID to the CONTEXTIDR register"
464 depends on CPU_COPY_V6
466 Enabling this option causes the kernel to write the current PID to
467 the PROCID field of the CONTEXTIDR register, at the expense of some
468 additional instructions during context switch. Say Y here only if you
469 are planning to use hardware trace tools with this kernel.