Kconfig.debug 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150
  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. config DEBUG_ERRORS
  56. bool "Verbose kernel error messages"
  57. depends on DEBUG_KERNEL
  58. help
  59. This option controls verbose debugging information which can be
  60. printed when the kernel detects an internal error. This debugging
  61. information is useful to kernel hackers when tracking down problems,
  62. but mostly meaningless to other people. It's safe to say Y unless
  63. you are concerned with the code size or don't want to see these
  64. messages.
  65. config DEBUG_STACK_USAGE
  66. bool "Enable stack utilization instrumentation"
  67. depends on DEBUG_KERNEL
  68. help
  69. Enables the display of the minimum amount of free stack which each
  70. task has ever had available in the sysrq-T output.
  71. # These options are only for real kernel hackers who want to get their hands dirty.
  72. config DEBUG_LL
  73. bool "Kernel low-level debugging functions"
  74. depends on DEBUG_KERNEL
  75. help
  76. Say Y here to include definitions of printascii, printch, printhex
  77. in the kernel. This is helpful if you are debugging code that
  78. executes before the console is initialized.
  79. config EARLY_PRINTK
  80. bool "Early printk"
  81. depends on DEBUG_LL
  82. help
  83. Say Y here if you want to have an early console using the
  84. kernel low-level debugging functions. Add earlyprintk to your
  85. kernel parameters to enable this console.
  86. config DEBUG_ICEDCC
  87. bool "Kernel low-level debugging via EmbeddedICE DCC channel"
  88. depends on DEBUG_LL
  89. help
  90. Say Y here if you want the debug print routines to direct their
  91. output to the EmbeddedICE macrocell's DCC channel using
  92. co-processor 14. This is known to work on the ARM9 style ICE
  93. channel and on the XScale with the PEEDI.
  94. It does include a timeout to ensure that the system does not
  95. totally freeze when there is nothing connected to read.
  96. config OC_ETM
  97. bool "On-chip ETM and ETB"
  98. select ARM_AMBA
  99. help
  100. Enables the on-chip embedded trace macrocell and embedded trace
  101. buffer driver that will allow you to collect traces of the
  102. kernel code.
  103. config DEBUG_DC21285_PORT
  104. bool "Kernel low-level debugging messages via footbridge serial port"
  105. depends on DEBUG_LL && FOOTBRIDGE
  106. help
  107. Say Y here if you want the debug print routines to direct their
  108. output to the serial port in the DC21285 (Footbridge). Saying N
  109. will cause the debug messages to appear on the first 16550
  110. serial port.
  111. config DEBUG_CLPS711X_UART2
  112. bool "Kernel low-level debugging messages via UART2"
  113. depends on DEBUG_LL && ARCH_CLPS711X
  114. help
  115. Say Y here if you want the debug print routines to direct their
  116. output to the second serial port on these devices. Saying N will
  117. cause the debug messages to appear on the first serial port.
  118. config DEBUG_S3C_UART
  119. depends on PLAT_SAMSUNG
  120. int "S3C UART to use for low-level debug"
  121. default "0"
  122. help
  123. Choice for UART for kernel low-level using S3C UARTS,
  124. should be between zero and two. The port must have been
  125. initialised by the boot-loader before use.
  126. The uncompressor code port configuration is now handled
  127. by CONFIG_S3C_LOWLEVEL_UART_PORT.
  128. endmenu