Kconfig.debug 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335
  1. menu "Kernel hacking"
  2. source "lib/Kconfig.debug"
  3. config STRICT_DEVMEM
  4. bool "Filter access to /dev/mem"
  5. depends on MMU
  6. ---help---
  7. If this option is disabled, you allow userspace (root) access to all
  8. of memory, including kernel and userspace memory. Accidental
  9. access to this is obviously disastrous, but specific access can
  10. be used by people debugging the kernel.
  11. If this option is switched on, the /dev/mem file only allows
  12. userspace access to memory mapped peripherals.
  13. If in doubt, say Y.
  14. # RMK wants arm kernels compiled with frame pointers or stack unwinding.
  15. # If you know what you are doing and are willing to live without stack
  16. # traces, you can get a slightly smaller kernel by setting this option to
  17. # n, but then RMK will have to kill you ;).
  18. config FRAME_POINTER
  19. bool
  20. depends on !THUMB2_KERNEL
  21. default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER
  22. help
  23. If you say N here, the resulting kernel will be slightly smaller and
  24. faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,
  25. when a problem occurs with the kernel, the information that is
  26. reported is severely limited.
  27. config ARM_UNWIND
  28. bool "Enable stack unwinding support (EXPERIMENTAL)"
  29. depends on AEABI && EXPERIMENTAL
  30. default y
  31. help
  32. This option enables stack unwinding support in the kernel
  33. using the information automatically generated by the
  34. compiler. The resulting kernel image is slightly bigger but
  35. the performance is not affected. Currently, this feature
  36. only works with EABI compilers. If unsure say Y.
  37. config OLD_MCOUNT
  38. bool
  39. depends on FUNCTION_TRACER && FRAME_POINTER
  40. default y
  41. config DEBUG_USER
  42. bool "Verbose user fault messages"
  43. help
  44. When a user program crashes due to an exception, the kernel can
  45. print a brief message explaining what the problem was. This is
  46. sometimes helpful for debugging but serves no purpose on a
  47. production system. Most people should say N here.
  48. In addition, you need to pass user_debug=N on the kernel command
  49. line to enable this feature. N consists of the sum of:
  50. 1 - undefined instruction events
  51. 2 - system calls
  52. 4 - invalid data aborts
  53. 8 - SIGSEGV faults
  54. 16 - SIGBUS faults
  55. # These options are only for real kernel hackers who want to get their hands dirty.
  56. config DEBUG_LL
  57. bool "Kernel low-level debugging functions (read help!)"
  58. depends on DEBUG_KERNEL
  59. help
  60. Say Y here to include definitions of printascii, printch, printhex
  61. in the kernel. This is helpful if you are debugging code that
  62. executes before the console is initialized.
  63. Note that selecting this option will limit the kernel to a single
  64. UART definition, as specified below. Attempting to boot the kernel
  65. image on a different platform *will not work*, so this option should
  66. not be enabled for kernels that are intended to be portable.
  67. choice
  68. prompt "Kernel low-level debugging port"
  69. depends on DEBUG_LL
  70. config DEBUG_LL_UART_NONE
  71. bool "No low-level debugging UART"
  72. help
  73. Say Y here if your platform doesn't provide a UART option
  74. below. This relies on your platform choosing the right UART
  75. definition internally in order for low-level debugging to
  76. work.
  77. config DEBUG_ICEDCC
  78. bool "Kernel low-level debugging via EmbeddedICE DCC channel"
  79. help
  80. Say Y here if you want the debug print routines to direct
  81. their output to the EmbeddedICE macrocell's DCC channel using
  82. co-processor 14. This is known to work on the ARM9 style ICE
  83. channel and on the XScale with the PEEDI.
  84. Note that the system will appear to hang during boot if there
  85. is nothing connected to read from the DCC.
  86. config DEBUG_SEMIHOSTING
  87. bool "Kernel low-level debug output via semihosting I"
  88. help
  89. Semihosting enables code running on an ARM target to use
  90. the I/O facilities on a host debugger/emulator through a
  91. simple SVC calls. The host debugger or emulator must have
  92. semihosting enabled for the special svc call to be trapped
  93. otherwise the kernel will crash.
  94. This is known to work with OpenOCD, as wellas
  95. ARM's Fast Models, or any other controlling environment
  96. that implements semihosting.
  97. For more details about semihosting, please see
  98. chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
  99. config AT91_DEBUG_LL_DBGU0
  100. bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
  101. depends on HAVE_AT91_DBGU0
  102. config AT91_DEBUG_LL_DBGU1
  103. bool "Kernel low-level debugging on 9263, 9g45 and cap9"
  104. depends on HAVE_AT91_DBGU1
  105. config DEBUG_FOOTBRIDGE_COM1
  106. bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
  107. depends on FOOTBRIDGE
  108. help
  109. Say Y here if you want the debug print routines to direct
  110. their output to the 8250 at PCI COM1.
  111. config DEBUG_DC21285_PORT
  112. bool "Kernel low-level debugging messages via footbridge serial port"
  113. depends on FOOTBRIDGE
  114. help
  115. Say Y here if you want the debug print routines to direct
  116. their output to the serial port in the DC21285 (Footbridge).
  117. config DEBUG_CLPS711X_UART1
  118. bool "Kernel low-level debugging messages via UART1"
  119. depends on ARCH_CLPS711X
  120. help
  121. Say Y here if you want the debug print routines to direct
  122. their output to the first serial port on these devices.
  123. config DEBUG_CLPS711X_UART2
  124. bool "Kernel low-level debugging messages via UART2"
  125. depends on ARCH_CLPS711X
  126. help
  127. Say Y here if you want the debug print routines to direct
  128. their output to the second serial port on these devices.
  129. config DEBUG_HIGHBANK_UART
  130. bool "Kernel low-level debugging messages via Highbank UART"
  131. depends on ARCH_HIGHBANK
  132. help
  133. Say Y here if you want the debug print routines to direct
  134. their output to the UART on Highbank based devices.
  135. config DEBUG_IMX1_UART
  136. bool "i.MX1 Debug UART"
  137. depends on SOC_IMX1
  138. help
  139. Say Y here if you want kernel low-level debugging support
  140. on i.MX1.
  141. config DEBUG_IMX23_UART
  142. bool "i.MX23 Debug UART"
  143. depends on SOC_IMX23
  144. help
  145. Say Y here if you want kernel low-level debugging support
  146. on i.MX23.
  147. config DEBUG_IMX25_UART
  148. bool "i.MX25 Debug UART"
  149. depends on SOC_IMX25
  150. help
  151. Say Y here if you want kernel low-level debugging support
  152. on i.MX25.
  153. config DEBUG_IMX21_IMX27_UART
  154. bool "i.MX21 and i.MX27 Debug UART"
  155. depends on SOC_IMX21 || SOC_IMX27
  156. help
  157. Say Y here if you want kernel low-level debugging support
  158. on i.MX21 or i.MX27.
  159. config DEBUG_IMX28_UART
  160. bool "i.MX28 Debug UART"
  161. depends on SOC_IMX28
  162. help
  163. Say Y here if you want kernel low-level debugging support
  164. on i.MX28.
  165. config DEBUG_IMX31_IMX35_UART
  166. bool "i.MX31 and i.MX35 Debug UART"
  167. depends on SOC_IMX31 || SOC_IMX35
  168. help
  169. Say Y here if you want kernel low-level debugging support
  170. on i.MX31 or i.MX35.
  171. config DEBUG_IMX51_UART
  172. bool "i.MX51 Debug UART"
  173. depends on SOC_IMX51
  174. help
  175. Say Y here if you want kernel low-level debugging support
  176. on i.MX51.
  177. config DEBUG_IMX50_IMX53_UART
  178. bool "i.MX50 and i.MX53 Debug UART"
  179. depends on SOC_IMX50 || SOC_IMX53
  180. help
  181. Say Y here if you want kernel low-level debugging support
  182. on i.MX50 or i.MX53.
  183. config DEBUG_IMX6Q_UART
  184. bool "i.MX6Q Debug UART"
  185. depends on SOC_IMX6Q
  186. help
  187. Say Y here if you want kernel low-level debugging support
  188. on i.MX6Q.
  189. config DEBUG_S3C_UART0
  190. depends on PLAT_SAMSUNG
  191. bool "Use S3C UART 0 for low-level debug"
  192. help
  193. Say Y here if you want the debug print routines to direct
  194. their output to UART 0. The port must have been initialised
  195. by the boot-loader before use.
  196. The uncompressor code port configuration is now handled
  197. by CONFIG_S3C_LOWLEVEL_UART_PORT.
  198. config DEBUG_S3C_UART1
  199. depends on PLAT_SAMSUNG
  200. bool "Use S3C UART 1 for low-level debug"
  201. help
  202. Say Y here if you want the debug print routines to direct
  203. their output to UART 1. The port must have been initialised
  204. by the boot-loader before use.
  205. The uncompressor code port configuration is now handled
  206. by CONFIG_S3C_LOWLEVEL_UART_PORT.
  207. config DEBUG_S3C_UART2
  208. depends on PLAT_SAMSUNG
  209. bool "Use S3C UART 2 for low-level debug"
  210. help
  211. Say Y here if you want the debug print routines to direct
  212. their output to UART 2. The port must have been initialised
  213. by the boot-loader before use.
  214. The uncompressor code port configuration is now handled
  215. by CONFIG_S3C_LOWLEVEL_UART_PORT.
  216. config DEBUG_REALVIEW_STD_PORT
  217. bool "RealView Default UART"
  218. depends on ARCH_REALVIEW
  219. help
  220. Say Y here if you want the debug print routines to direct
  221. their output to the serial port on RealView EB, PB11MP, PBA8
  222. and PBX platforms.
  223. config DEBUG_REALVIEW_PB1176_PORT
  224. bool "RealView PB1176 UART"
  225. depends on MACH_REALVIEW_PB1176
  226. help
  227. Say Y here if you want the debug print routines to direct
  228. their output to the standard serial port on the RealView
  229. PB1176 platform.
  230. config DEBUG_MSM_UART1
  231. bool "Kernel low-level debugging messages via MSM UART1"
  232. depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
  233. help
  234. Say Y here if you want the debug print routines to direct
  235. their output to the first serial port on MSM devices.
  236. config DEBUG_MSM_UART2
  237. bool "Kernel low-level debugging messages via MSM UART2"
  238. depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
  239. help
  240. Say Y here if you want the debug print routines to direct
  241. their output to the second serial port on MSM devices.
  242. config DEBUG_MSM_UART3
  243. bool "Kernel low-level debugging messages via MSM UART3"
  244. depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
  245. help
  246. Say Y here if you want the debug print routines to direct
  247. their output to the third serial port on MSM devices.
  248. config DEBUG_MSM8660_UART
  249. bool "Kernel low-level debugging messages via MSM 8660 UART"
  250. depends on ARCH_MSM8X60
  251. select MSM_HAS_DEBUG_UART_HS
  252. help
  253. Say Y here if you want the debug print routines to direct
  254. their output to the serial port on MSM 8660 devices.
  255. config DEBUG_MSM8960_UART
  256. bool "Kernel low-level debugging messages via MSM 8960 UART"
  257. depends on ARCH_MSM8960
  258. select MSM_HAS_DEBUG_UART_HS
  259. help
  260. Say Y here if you want the debug print routines to direct
  261. their output to the serial port on MSM 8960 devices.
  262. endchoice
  263. config EARLY_PRINTK
  264. bool "Early printk"
  265. depends on DEBUG_LL
  266. help
  267. Say Y here if you want to have an early console using the
  268. kernel low-level debugging functions. Add earlyprintk to your
  269. kernel parameters to enable this console.
  270. config OC_ETM
  271. bool "On-chip ETM and ETB"
  272. depends on ARM_AMBA
  273. help
  274. Enables the on-chip embedded trace macrocell and embedded trace
  275. buffer driver that will allow you to collect traces of the
  276. kernel code.
  277. config ARM_KPROBES_TEST
  278. tristate "Kprobes test module"
  279. depends on KPROBES && MODULES
  280. help
  281. Perform tests of kprobes API and instruction set simulation.
  282. endmenu