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