1menu "Kernel hacking"
 2
 3source "lib/Kconfig.debug"
 4
 5config EARLY_PRINTK
 6	bool "Early printk" if EXPERT && 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_EXTRA_FLAGS
25	string "Additional compiler arguments when building with '-g'"
26	depends on DEBUG_INFO
27	default ""
28	help
29	  Debug info can be large, and flags like
30	  `-femit-struct-debug-baseonly' can reduce the kernel file
31	  size and build time noticeably.  Such flags are often
32	  helpful if the main use of debug info is line number info.
33
34endmenu

 1menu "Kernel hacking"
 2
 3source "lib/Kconfig.debug"
 4
 5config EARLY_PRINTK
 6	bool "Early printk" if EXPERT && 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 TILE_HVGLUE_TRACE
18	bool "Provide wrapper functions for hypervisor ABI calls"
19	default n
20	help
21	  Provide wrapper functions for the hypervisor ABI calls
22	  defined in arch/tile/kernel/hvglue.S.  This allows tracing
23	  mechanisms, etc., to have visibility into those calls.
 
 
 
 
 
 
 
 
 
24
25endmenu