Kconfig.debug 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335
  1. menu "Kernel hacking"
  2. source "lib/Kconfig.debug"
  3. config PPC_DISABLE_WERROR
  4. bool "Don't build arch/powerpc code with -Werror"
  5. default n
  6. help
  7. This option tells the compiler NOT to build the code under
  8. arch/powerpc with the -Werror flag (which means warnings
  9. are treated as errors).
  10. Only enable this if you are hitting a build failure in the
  11. arch/powerpc code caused by a warning, and you don't feel
  12. inclined to fix it.
  13. config PPC_WERROR
  14. bool
  15. depends on !PPC_DISABLE_WERROR
  16. default y
  17. config PRINT_STACK_DEPTH
  18. int "Stack depth to print" if DEBUG_KERNEL
  19. default 64
  20. help
  21. This option allows you to set the stack depth that the kernel
  22. prints in stack traces. This can be useful if your display is
  23. too small and stack traces cause important information to
  24. scroll off the screen.
  25. config DEBUG_STACKOVERFLOW
  26. bool "Check for stack overflows"
  27. depends on DEBUG_KERNEL
  28. help
  29. This option will cause messages to be printed if free stack space
  30. drops below a certain limit.
  31. config HCALL_STATS
  32. bool "Hypervisor call instrumentation"
  33. depends on PPC_PSERIES && DEBUG_FS && TRACEPOINTS
  34. help
  35. Adds code to keep track of the number of hypervisor calls made and
  36. the amount of time spent in hypervisor calls. Wall time spent in
  37. each call is always calculated, and if available CPU cycles spent
  38. are also calculated. A directory named hcall_inst is added at the
  39. root of the debugfs filesystem. Within the hcall_inst directory
  40. are files that contain CPU specific call statistics.
  41. This option will add a small amount of overhead to all hypervisor
  42. calls.
  43. config PPC_EMULATED_STATS
  44. bool "Emulated instructions tracking"
  45. depends on DEBUG_FS
  46. help
  47. Adds code to keep track of the number of instructions that are
  48. emulated by the in-kernel emulator. Counters for the various classes
  49. of emulated instructions are available under
  50. powerpc/emulated_instructions/ in the root of the debugfs file
  51. system. Optionally (controlled by
  52. powerpc/emulated_instructions/do_warn in debugfs), rate-limited
  53. warnings can be printed to the console when instructions are
  54. emulated.
  55. config CODE_PATCHING_SELFTEST
  56. bool "Run self-tests of the code-patching code."
  57. depends on DEBUG_KERNEL
  58. default n
  59. config FTR_FIXUP_SELFTEST
  60. bool "Run self-tests of the feature-fixup code."
  61. depends on DEBUG_KERNEL
  62. default n
  63. config MSI_BITMAP_SELFTEST
  64. bool "Run self-tests of the MSI bitmap code."
  65. depends on DEBUG_KERNEL
  66. default n
  67. config XMON
  68. bool "Include xmon kernel debugger"
  69. depends on DEBUG_KERNEL
  70. help
  71. Include in-kernel hooks for the xmon kernel monitor/debugger.
  72. Unless you are intending to debug the kernel, say N here.
  73. Make sure to enable also CONFIG_BOOTX_TEXT on Macs. Otherwise
  74. nothing will appear on the screen (xmon writes directly to the
  75. framebuffer memory).
  76. The cmdline option 'xmon' or 'xmon=early' will drop into xmon
  77. very early during boot. 'xmon=on' will just enable the xmon
  78. debugger hooks. 'xmon=off' will disable the debugger hooks
  79. if CONFIG_XMON_DEFAULT is set.
  80. xmon will print a backtrace on the very first invocation.
  81. 'xmon=nobt' will disable this autobacktrace.
  82. config XMON_DEFAULT
  83. bool "Enable xmon by default"
  84. depends on XMON
  85. help
  86. xmon is normally disabled unless booted with 'xmon=on'.
  87. Use 'xmon=off' to disable xmon init during runtime.
  88. config XMON_DISASSEMBLY
  89. bool "Include disassembly support in xmon"
  90. depends on XMON
  91. default y
  92. help
  93. Include support for disassembling in xmon. You probably want
  94. to say Y here, unless you're building for a memory-constrained
  95. system.
  96. config DEBUGGER
  97. bool
  98. depends on KGDB || XMON
  99. default y
  100. config BDI_SWITCH
  101. bool "Include BDI-2000 user context switcher"
  102. depends on DEBUG_KERNEL && PPC32
  103. help
  104. Include in-kernel support for the Abatron BDI2000 debugger.
  105. Unless you are intending to debug the kernel with one of these
  106. machines, say N here.
  107. config BOOTX_TEXT
  108. bool "Support for early boot text console (BootX or OpenFirmware only)"
  109. depends on PPC_OF && PPC_BOOK3S
  110. help
  111. Say Y here to see progress messages from the boot firmware in text
  112. mode. Requires either BootX or Open Firmware.
  113. config PPC_EARLY_DEBUG
  114. bool "Early debugging (dangerous)"
  115. help
  116. Say Y to enable some early debugging facilities that may be available
  117. for your processor/board combination. Those facilities are hacks
  118. intended to debug problems early during boot, this should not be
  119. enabled in a production kernel.
  120. Note that enabling this will also cause the kernel default log level
  121. to be pushed to max automatically very early during boot
  122. choice
  123. prompt "Early debugging console"
  124. depends on PPC_EARLY_DEBUG
  125. help
  126. Use the selected console for early debugging. Careful, if you
  127. enable debugging for the wrong type of machine your kernel
  128. _will not boot_.
  129. config PPC_EARLY_DEBUG_LPAR
  130. bool "LPAR HV Console"
  131. depends on PPC_PSERIES
  132. help
  133. Select this to enable early debugging for a machine with a HVC
  134. console on vterm 0.
  135. config PPC_EARLY_DEBUG_LPAR_HVSI
  136. bool "LPAR HVSI Console"
  137. depends on PPC_PSERIES
  138. help
  139. Select this to enable early debugging for a machine with a HVSI
  140. console on a specified vterm.
  141. config PPC_EARLY_DEBUG_G5
  142. bool "Apple G5"
  143. depends on PPC_PMAC64
  144. help
  145. Select this to enable early debugging for Apple G5 machines.
  146. config PPC_EARLY_DEBUG_RTAS_PANEL
  147. bool "RTAS Panel"
  148. depends on PPC_RTAS
  149. help
  150. Select this to enable early debugging via the RTAS panel.
  151. config PPC_EARLY_DEBUG_RTAS_CONSOLE
  152. bool "RTAS Console"
  153. depends on PPC_RTAS
  154. select UDBG_RTAS_CONSOLE
  155. help
  156. Select this to enable early debugging via the RTAS console.
  157. config PPC_EARLY_DEBUG_MAPLE
  158. bool "Maple real mode"
  159. depends on PPC_MAPLE
  160. help
  161. Select this to enable early debugging for Maple.
  162. config PPC_EARLY_DEBUG_PAS_REALMODE
  163. bool "PA Semi real mode"
  164. depends on PPC_PASEMI
  165. help
  166. Select this to enable early debugging for PA Semi.
  167. Output will be on UART0.
  168. config PPC_EARLY_DEBUG_BEAT
  169. bool "Beat HV Console"
  170. depends on PPC_CELLEB
  171. select PPC_UDBG_BEAT
  172. help
  173. Select this to enable early debugging for Celleb with Beat.
  174. config PPC_EARLY_DEBUG_44x
  175. bool "Early serial debugging for IBM/AMCC 44x CPUs"
  176. # PPC_EARLY_DEBUG on 440 leaves AS=1 mappings above the TLB high water
  177. # mark, which doesn't work with current 440 KVM.
  178. depends on 44x && !KVM
  179. help
  180. Select this to enable early debugging for IBM 44x chips via the
  181. inbuilt serial port. If you enable this, ensure you set
  182. PPC_EARLY_DEBUG_44x_PHYSLOW below to suit your target board.
  183. config PPC_EARLY_DEBUG_40x
  184. bool "Early serial debugging for IBM/AMCC 40x CPUs"
  185. depends on 40x
  186. help
  187. Select this to enable early debugging for IBM 40x chips via the
  188. inbuilt serial port. This works on chips with a 16550 compatible
  189. UART. Xilinx chips with uartlite cannot use this option.
  190. config PPC_EARLY_DEBUG_CPM
  191. bool "Early serial debugging for Freescale CPM-based serial ports"
  192. depends on SERIAL_CPM
  193. select PIN_TLB if PPC_8xx
  194. help
  195. Select this to enable early debugging for Freescale chips
  196. using a CPM-based serial port. This assumes that the bootwrapper
  197. has run, and set up the CPM in a particular way.
  198. config PPC_EARLY_DEBUG_USBGECKO
  199. bool "Early debugging through the USB Gecko adapter"
  200. depends on GAMECUBE_COMMON
  201. select USBGECKO_UDBG
  202. help
  203. Select this to enable early debugging for Nintendo GameCube/Wii
  204. consoles via an external USB Gecko adapter.
  205. config PPC_EARLY_DEBUG_WSP
  206. bool "Early debugging via WSP's internal UART"
  207. depends on PPC_WSP
  208. select PPC_UDBG_16550
  209. config PPC_EARLY_DEBUG_PS3GELIC
  210. bool "Early debugging through the PS3 Ethernet port"
  211. depends on PPC_PS3
  212. select PS3GELIC_UDBG
  213. help
  214. Select this to enable early debugging for the PlayStation3 via
  215. UDP broadcasts sent out through the Ethernet port.
  216. config PPC_EARLY_DEBUG_OPAL_RAW
  217. bool "OPAL raw console"
  218. depends on HVC_OPAL
  219. help
  220. Select this to enable early debugging for the PowerNV platform
  221. using a "raw" console
  222. config PPC_EARLY_DEBUG_OPAL_HVSI
  223. bool "OPAL hvsi console"
  224. depends on HVC_OPAL
  225. help
  226. Select this to enable early debugging for the PowerNV platform
  227. using an "hvsi" console
  228. endchoice
  229. config PPC_EARLY_DEBUG_OPAL
  230. def_bool y
  231. depends on PPC_EARLY_DEBUG_OPAL_RAW || PPC_EARLY_DEBUG_OPAL_HVSI
  232. config PPC_EARLY_DEBUG_HVSI_VTERMNO
  233. hex "vterm number to use with early debug HVSI"
  234. depends on PPC_EARLY_DEBUG_LPAR_HVSI
  235. default "0x30000000"
  236. help
  237. You probably want 0x30000000 for your first serial port and
  238. 0x30000001 for your second one
  239. config PPC_EARLY_DEBUG_OPAL_VTERMNO
  240. hex "vterm number to use with OPAL early debug"
  241. depends on PPC_EARLY_DEBUG_OPAL
  242. default "0"
  243. help
  244. This correspond to which /dev/hvcN you want to use for early
  245. debug.
  246. On OPAL v1 (takeover) this should always be 0
  247. On OPAL v2, this will be 0 for network console and 1 or 2 for
  248. the machine built-in serial ports.
  249. config PPC_EARLY_DEBUG_44x_PHYSLOW
  250. hex "Low 32 bits of early debug UART physical address"
  251. depends on PPC_EARLY_DEBUG_44x
  252. default "0x40000200"
  253. help
  254. You probably want 0x40000200 for ebony boards and
  255. 0x40000300 for taishan
  256. config PPC_EARLY_DEBUG_44x_PHYSHIGH
  257. hex "EPRN of early debug UART physical address"
  258. depends on PPC_EARLY_DEBUG_44x
  259. default "0x1"
  260. config PPC_EARLY_DEBUG_40x_PHYSADDR
  261. hex "Early debug UART physical address"
  262. depends on PPC_EARLY_DEBUG_40x
  263. default "0xef600300"
  264. config PPC_EARLY_DEBUG_CPM_ADDR
  265. hex "CPM UART early debug transmit descriptor address"
  266. depends on PPC_EARLY_DEBUG_CPM
  267. default "0xfa202008" if PPC_EP88XC
  268. default "0xf0001ff8" if CPM2
  269. default "0xff002008" if CPM1
  270. help
  271. This specifies the address of the transmit descriptor
  272. used for early debug output. Because it is needed before
  273. platform probing is done, all platforms selected must
  274. share the same address.
  275. config STRICT_DEVMEM
  276. def_bool y
  277. prompt "Filter access to /dev/mem"
  278. help
  279. This option restricts access to /dev/mem. If this option is
  280. disabled, you allow userspace access to all memory, including
  281. kernel and userspace memory. Accidental memory access is likely
  282. to be disastrous.
  283. Memory access is required for experts who want to debug the kernel.
  284. If you are unsure, say Y.
  285. endmenu