1menu "Kernel hacking"
2
3config TRACE_IRQFLAGS_SUPPORT
4	def_bool y
5
6source "lib/Kconfig.debug"
7
8config SH_STANDARD_BIOS
9	bool "Use LinuxSH standard BIOS"
10	depends on SUPERH32
11	help
12	  Say Y here if your target has the gdb-sh-stub
13	  package from www.m17n.org (or any conforming standard LinuxSH BIOS)
14	  in FLASH or EPROM.  The kernel will use standard BIOS calls during
15	  boot for various housekeeping tasks (including calls to read and
16	  write characters to a system console, get a MAC address from an
17	  on-board Ethernet interface, and shut down the hardware).  Note this
18	  does not work with machines with an existing operating system in
19	  mask ROM and no flash (WindowsCE machines fall in this category).
20	  If unsure, say N.
21
22config STACK_DEBUG
23	bool "Check for stack overflows"
24	depends on DEBUG_KERNEL && SUPERH32
25	help
26	  This option will cause messages to be printed if free stack space
27	  drops below a certain limit. Saying Y here will add overhead to
28	  every function call and will therefore incur a major
29	  performance hit. Most users should say N.
30
31config 4KSTACKS
32	bool "Use 4Kb for kernel stacks instead of 8Kb"
33	depends on DEBUG_KERNEL && (MMU || BROKEN) && !PAGE_SIZE_64KB
34	help
35	  If you say Y here the kernel will use a 4Kb stacksize for the
36	  kernel stack attached to each process/thread. This facilitates
37	  running more threads on a system and also reduces the pressure
38	  on the VM subsystem for higher order allocations. This option
39	  will also use IRQ stacks to compensate for the reduced stackspace.
40
41config IRQSTACKS
42	bool "Use separate kernel stacks when processing interrupts"
43	depends on DEBUG_KERNEL && SUPERH32 && BROKEN
44	help
45	  If you say Y here the kernel will use separate kernel stacks
46	  for handling hard and soft interrupts.  This can help avoid
47	  overflowing the process kernel stacks.
48
49config DUMP_CODE
50	bool "Show disassembly of nearby code in register dumps"
51	depends on DEBUG_KERNEL && SUPERH32
52	default y if DEBUG_BUGVERBOSE
53	default n
54	help
55	  This prints out a code trace of the instructions leading up to
56	  the faulting instruction as a debugging aid. As this does grow
57	  the kernel in size a bit, most users will want to say N here.
58
59	  Those looking for more verbose debugging output should say Y.
60
61config DWARF_UNWINDER
62	bool "Enable the DWARF unwinder for stacktraces"
63	select FRAME_POINTER
64	depends on SUPERH32
65	default n
66	help
67	  Enabling this option will make stacktraces more accurate, at
68	  the cost of an increase in overall kernel size.
69
70config SH_NO_BSS_INIT
71	bool "Avoid zeroing BSS (to speed-up startup on suitable platforms)"
72	depends on DEBUG_KERNEL
73	default n
74	help
75	  If running in painfully slow environments, such as an RTL
76	  simulation or from remote memory via SHdebug, where the memory
77	  can already be guaranteed to ber zeroed on boot, say Y.
78
79	  For all other cases, say N. If this option seems perplexing, or
80	  you aren't sure, say N.
81
82config SH64_SR_WATCH
83	bool "Debug: set SR.WATCH to enable hardware watchpoints and trace"
84	depends on SUPERH64
85
86config MCOUNT
87	def_bool y
88	depends on SUPERH32
89	depends on STACK_DEBUG || FUNCTION_TRACER
90
91endmenu
92