3 source "lib/Kconfig.debug"
5 # RMK wants arm kernels compiled with frame pointers or stack unwinding.
6 # If you know what you are doing and are willing to live without stack
7 # traces, you can get a slightly smaller kernel by setting this option to
8 # n, but then RMK will have to kill you ;).
11 depends on !THUMB2_KERNEL
12 default y if !ARM_UNWIND
14 If you say N here, the resulting kernel will be slightly smaller and
15 faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
16 when a problem occurs with the kernel, the information that is
17 reported is severely limited.
20 bool "Enable stack unwinding support"
21 depends on AEABI && EXPERIMENTAL
24 This option enables stack unwinding support in the kernel
25 using the information automatically generated by the
26 compiler. The resulting kernel image is slightly bigger but
27 the performance is not affected. Currently, this feature
28 only works with EABI compilers. If unsure say Y.
32 depends on FUNCTION_TRACER && FRAME_POINTER
36 bool "Verbose user fault messages"
38 When a user program crashes due to an exception, the kernel can
39 print a brief message explaining what the problem was. This is
40 sometimes helpful for debugging but serves no purpose on a
41 production system. Most people should say N here.
43 In addition, you need to pass user_debug=N on the kernel command
44 line to enable this feature. N consists of the sum of:
46 1 - undefined instruction events
48 4 - invalid data aborts
53 bool "Verbose kernel error messages"
54 depends on DEBUG_KERNEL
56 This option controls verbose debugging information which can be
57 printed when the kernel detects an internal error. This debugging
58 information is useful to kernel hackers when tracking down problems,
59 but mostly meaningless to other people. It's safe to say Y unless
60 you are concerned with the code size or don't want to see these
63 config DEBUG_STACK_USAGE
64 bool "Enable stack utilization instrumentation"
65 depends on DEBUG_KERNEL
67 Enables the display of the minimum amount of free stack which each
68 task has ever had available in the sysrq-T output.
70 # These options are only for real kernel hackers who want to get their hands dirty.
72 bool "Kernel low-level debugging functions"
73 depends on DEBUG_KERNEL
75 Say Y here to include definitions of printascii, printch, printhex
76 in the kernel. This is helpful if you are debugging code that
77 executes before the console is initialized.
83 Say Y here if you want to have an early console using the
84 kernel low-level debugging functions. Add earlyprintk to your
85 kernel parameters to enable this console.
88 bool "Kernel low-level debugging via EmbeddedICE DCC channel"
91 Say Y here if you want the debug print routines to direct their
92 output to the EmbeddedICE macrocell's DCC channel using
93 co-processor 14. This is known to work on the ARM9 style ICE
94 channel and on the XScale with the PEEDI.
96 It does include a timeout to ensure that the system does not
97 totally freeze when there is nothing connected to read.
100 bool "On-chip ETM and ETB"
103 Enables the on-chip embedded trace macrocell and embedded trace
104 buffer driver that will allow you to collect traces of the
107 config DEBUG_DC21285_PORT
108 bool "Kernel low-level debugging messages via footbridge serial port"
109 depends on DEBUG_LL && FOOTBRIDGE
111 Say Y here if you want the debug print routines to direct their
112 output to the serial port in the DC21285 (Footbridge). Saying N
113 will cause the debug messages to appear on the first 16550
116 config DEBUG_CLPS711X_UART2
117 bool "Kernel low-level debugging messages via UART2"
118 depends on DEBUG_LL && ARCH_CLPS711X
120 Say Y here if you want the debug print routines to direct their
121 output to the second serial port on these devices. Saying N will
122 cause the debug messages to appear on the first serial port.
124 config DEBUG_S3C_UART
125 depends on PLAT_SAMSUNG
126 int "S3C UART to use for low-level debug"
129 Choice for UART for kernel low-level using S3C UARTS,
130 should be between zero and two. The port must have been
131 initialised by the boot-loader before use.
133 The uncompressor code port configuration is now handled
134 by CONFIG_S3C_LOWLEVEL_UART_PORT.