Kconfig.debug 3.1 KB

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