1menu "Kernel hacking"
   4        def_bool y
   6source "lib/Kconfig.debug"
   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 (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.
  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.
  32        bool "Stack utilization instrumentation"
  33        depends on DEBUG_KERNEL
  34        help
  35          Enables the display of the minimum amount of free stack which each
  36          task has ever had available in the sysrq-T and sysrq-P debug output.
  38          This option will slow down process creation somewhat.
  40config 4KSTACKS
  41        bool "Use 4Kb for kernel stacks instead of 8Kb"
  42        depends on DEBUG_KERNEL && (MMU || BROKEN) && !PAGE_SIZE_64KB
  43        help
  44          If you say Y here the kernel will use a 4Kb stacksize for the
  45          kernel stack attached to each process/thread. This facilitates
  46          running more threads on a system and also reduces the pressure
  47          on the VM subsystem for higher order allocations. This option
  48          will also use IRQ stacks to compensate for the reduced stackspace.
  50config IRQSTACKS
  51        bool "Use separate kernel stacks when processing interrupts"
  52        depends on DEBUG_KERNEL && SUPERH32 && BROKEN
  53        help
  54          If you say Y here the kernel will use separate kernel stacks
  55          for handling hard and soft interrupts.  This can help avoid
  56          overflowing the process kernel stacks.
  58config DUMP_CODE
  59        bool "Show disassembly of nearby code in register dumps"
  60        depends on DEBUG_KERNEL && SUPERH32
  61        default y if DEBUG_BUGVERBOSE
  62        default n
  63        help
  64          This prints out a code trace of the instructions leading up to
  65          the faulting instruction as a debugging aid. As this does grow
  66          the kernel in size a bit, most users will want to say N here.
  68          Those looking for more verbose debugging output should say Y.
  71        bool "Enable the DWARF unwinder for stacktraces"
  72        select FRAME_POINTER
  73        default n
  74        help
  75          Enabling this option will make stacktraces more accurate, at
  76          the cost of an increase in overall kernel size.
  78config SH_NO_BSS_INIT
  79        bool "Avoid zeroing BSS (to speed-up startup on suitable platforms)"
  80        depends on DEBUG_KERNEL
  81        default n
  82        help
  83          If running in painfully slow environments, such as an RTL
  84          simulation or from remote memory via SHdebug, where the memory
  85          can already be gauranteed to ber zeroed on boot, say Y.
  87          For all other cases, say N. If this option seems perplexing, or
  88          you aren't sure, say N.
  90config SH64_SR_WATCH
  91        bool "Debug: set SR.WATCH to enable hardware watchpoints and trace"
  92        depends on SUPERH64
  94config MCOUNT
  95        def_bool y
  96        depends on SUPERH32
  97        depends on STACK_DEBUG || FUNCTION_TRACER