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 DEBUG_LL_UART_NONE
85 bool "No low-level debugging UART"
87 Say Y here if your platform doesn't provide a UART option
88 below. This relies on your platform choosing the right UART
89 definition internally in order for low-level debugging to
93 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
95 Say Y here if you want the debug print routines to direct
96 their output to the EmbeddedICE macrocell's DCC channel using
97 co-processor 14. This is known to work on the ARM9 style ICE
98 channel and on the XScale with the PEEDI.
100 Note that the system will appear to hang during boot if there
101 is nothing connected to read from the DCC.
103 config DEBUG_SEMIHOSTING
104 bool "Kernel low-level debug output via semihosting I"
106 Semihosting enables code running on an ARM target to use
107 the I/O facilities on a host debugger/emulator through a
108 simple SVC calls. The host debugger or emulator must have
109 semihosting enabled for the special svc call to be trapped
110 otherwise the kernel will crash.
112 This is known to work with OpenOCD, as wellas
113 ARM's Fast Models, or any other controlling environment
114 that implements semihosting.
116 For more details about semihosting, please see
117 chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
119 config AT91_DEBUG_LL_DBGU0
120 bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
121 depends on HAVE_AT91_DBGU0
123 config AT91_DEBUG_LL_DBGU1
124 bool "Kernel low-level debugging on 9263, 9g45 and cap9"
125 depends on HAVE_AT91_DBGU1
127 config DEBUG_FOOTBRIDGE_COM1
128 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
129 depends on FOOTBRIDGE
131 Say Y here if you want the debug print routines to direct
132 their output to the 8250 at PCI COM1.
134 config DEBUG_DC21285_PORT
135 bool "Kernel low-level debugging messages via footbridge serial port"
136 depends on FOOTBRIDGE
138 Say Y here if you want the debug print routines to direct
139 their output to the serial port in the DC21285 (Footbridge).
141 config DEBUG_CLPS711X_UART1
142 bool "Kernel low-level debugging messages via UART1"
143 depends on ARCH_CLPS711X
145 Say Y here if you want the debug print routines to direct
146 their output to the first serial port on these devices.
148 config DEBUG_CLPS711X_UART2
149 bool "Kernel low-level debugging messages via UART2"
150 depends on ARCH_CLPS711X
152 Say Y here if you want the debug print routines to direct
153 their output to the second serial port on these devices.
155 config DEBUG_HIGHBANK_UART
156 bool "Kernel low-level debugging messages via Highbank UART"
157 depends on ARCH_HIGHBANK
159 Say Y here if you want the debug print routines to direct
160 their output to the UART on Highbank based devices.
162 config DEBUG_IMX1_UART
163 bool "i.MX1 Debug UART"
166 Say Y here if you want kernel low-level debugging support
169 config DEBUG_IMX23_UART
170 bool "i.MX23 Debug UART"
173 Say Y here if you want kernel low-level debugging support
176 config DEBUG_IMX25_UART
177 bool "i.MX25 Debug UART"
180 Say Y here if you want kernel low-level debugging support
183 config DEBUG_IMX21_IMX27_UART
184 bool "i.MX21 and i.MX27 Debug UART"
185 depends on SOC_IMX21 || SOC_IMX27
187 Say Y here if you want kernel low-level debugging support
190 config DEBUG_IMX28_UART
191 bool "i.MX28 Debug UART"
194 Say Y here if you want kernel low-level debugging support
197 config DEBUG_IMX31_IMX35_UART
198 bool "i.MX31 and i.MX35 Debug UART"
199 depends on SOC_IMX31 || SOC_IMX35
201 Say Y here if you want kernel low-level debugging support
204 config DEBUG_IMX51_UART
205 bool "i.MX51 Debug UART"
208 Say Y here if you want kernel low-level debugging support
211 config DEBUG_IMX50_IMX53_UART
212 bool "i.MX50 and i.MX53 Debug UART"
213 depends on SOC_IMX50 || SOC_IMX53
215 Say Y here if you want kernel low-level debugging support
218 config DEBUG_IMX6Q_UART
219 bool "i.MX6Q Debug UART"
222 Say Y here if you want kernel low-level debugging support
225 config DEBUG_S3C_UART0
226 depends on PLAT_SAMSUNG
227 bool "Use S3C UART 0 for low-level debug"
229 Say Y here if you want the debug print routines to direct
230 their output to UART 0. The port must have been initialised
231 by the boot-loader before use.
233 The uncompressor code port configuration is now handled
234 by CONFIG_S3C_LOWLEVEL_UART_PORT.
236 config DEBUG_S3C_UART1
237 depends on PLAT_SAMSUNG
238 bool "Use S3C UART 1 for low-level debug"
240 Say Y here if you want the debug print routines to direct
241 their output to UART 1. The port must have been initialised
242 by the boot-loader before use.
244 The uncompressor code port configuration is now handled
245 by CONFIG_S3C_LOWLEVEL_UART_PORT.
247 config DEBUG_S3C_UART2
248 depends on PLAT_SAMSUNG
249 bool "Use S3C UART 2 for low-level debug"
251 Say Y here if you want the debug print routines to direct
252 their output to UART 2. The port must have been initialised
253 by the boot-loader before use.
255 The uncompressor code port configuration is now handled
256 by CONFIG_S3C_LOWLEVEL_UART_PORT.
258 config DEBUG_REALVIEW_STD_PORT
259 bool "RealView Default UART"
260 depends on ARCH_REALVIEW
262 Say Y here if you want the debug print routines to direct
263 their output to the serial port on RealView EB, PB11MP, PBA8
266 config DEBUG_REALVIEW_PB1176_PORT
267 bool "RealView PB1176 UART"
268 depends on MACH_REALVIEW_PB1176
270 Say Y here if you want the debug print routines to direct
271 their output to the standard serial port on the RealView
274 config DEBUG_MSM_UART1
275 bool "Kernel low-level debugging messages via MSM UART1"
276 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
278 Say Y here if you want the debug print routines to direct
279 their output to the first serial port on MSM devices.
281 config DEBUG_MSM_UART2
282 bool "Kernel low-level debugging messages via MSM UART2"
283 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
285 Say Y here if you want the debug print routines to direct
286 their output to the second serial port on MSM devices.
288 config DEBUG_MSM_UART3
289 bool "Kernel low-level debugging messages via MSM UART3"
290 depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
292 Say Y here if you want the debug print routines to direct
293 their output to the third serial port on MSM devices.
295 config DEBUG_MSM8660_UART
296 bool "Kernel low-level debugging messages via MSM 8660 UART"
297 depends on ARCH_MSM8X60
298 select MSM_HAS_DEBUG_UART_HS
300 Say Y here if you want the debug print routines to direct
301 their output to the serial port on MSM 8660 devices.
303 config DEBUG_MSM8960_UART
304 bool "Kernel low-level debugging messages via MSM 8960 UART"
305 depends on ARCH_MSM8960
306 select MSM_HAS_DEBUG_UART_HS
308 Say Y here if you want the debug print routines to direct
309 their output to the serial port on MSM 8960 devices.
317 Say Y here if you want to have an early console using the
318 kernel low-level debugging functions. Add earlyprintk to your
319 kernel parameters to enable this console.
322 bool "On-chip ETM and ETB"
325 Enables the on-chip embedded trace macrocell and embedded trace
326 buffer driver that will allow you to collect traces of the
329 config ARM_KPROBES_TEST
330 tristate "Kprobes test module"
331 depends on KPROBES && MODULES
333 Perform tests of kprobes API and instruction set simulation.