blob: a81f0fbf7e602ff12ede15e42e8f7ba869ffded1 [file] [log] [blame]
Chris Metcalf867e3592010-05-28 23:09:12 -04001menu "Kernel hacking"
2
3source "lib/Kconfig.debug"
4
5config EARLY_PRINTK
6 bool "Early printk" if EMBEDDED && DEBUG_KERNEL
7 default y
8 help
9 Write kernel log output directly via the hypervisor console.
10
11 This is useful for kernel debugging when your machine crashes very
12 early before the console code is initialized. For normal operation
13 it is not recommended because it looks ugly and doesn't cooperate
14 with klogd/syslogd. You should normally N here,
15 unless you want to debug such a crash.
16
17config DEBUG_STACKOVERFLOW
18 bool "Check for stack overflows"
19 depends on DEBUG_KERNEL
20 help
21 This option will cause messages to be printed if free stack space
22 drops below a certain limit.
23
24config DEBUG_STACK_USAGE
25 bool "Stack utilization instrumentation"
26 depends on DEBUG_KERNEL
27 help
28 Enables the display of the minimum amount of free stack which each
29 task has ever had available in the sysrq-T and sysrq-P debug output.
30
31 This option will slow down process creation somewhat.
32
33config DEBUG_EXTRA_FLAGS
34 string "Additional compiler arguments when building with '-g'"
35 depends on DEBUG_INFO
36 default ""
37 help
38 Debug info can be large, and flags like
39 `-femit-struct-debug-baseonly' can reduce the kernel file
40 size and build time noticeably. Such flags are often
41 helpful if the main use of debug info is line number info.
42
43endmenu