Kconfig.debug 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. menu "Kernel hacking"
  2. source "lib/Kconfig.debug"
  3. # RMK wants arm kernels compiled with frame pointers so hardwire this to y.
  4. # If you know what you are doing and are willing to live without stack
  5. # traces, you can get a slightly smaller kernel by setting this option to
  6. # n, but then RMK will have to kill you ;).
  7. config FRAME_POINTER
  8. bool
  9. default y
  10. help
  11. If you say N here, the resulting kernel will be slightly smaller and
  12. faster. However, when a problem occurs with the kernel, the
  13. information that is reported is severely limited. Most people
  14. should say Y here.
  15. config DEBUG_USER
  16. bool "Verbose user fault messages"
  17. help
  18. When a user program crashes due to an exception, the kernel can
  19. print a brief message explaining what the problem was. This is
  20. sometimes helpful for debugging but serves no purpose on a
  21. production system. Most people should say N here.
  22. In addition, you need to pass user_debug=N on the kernel command
  23. line to enable this feature. N consists of the sum of:
  24. 1 - undefined instruction events
  25. 2 - system calls
  26. 4 - invalid data aborts
  27. 8 - SIGSEGV faults
  28. 16 - SIGBUS faults
  29. config DEBUG_ERRORS
  30. bool "Verbose kernel error messages"
  31. depends on DEBUG_KERNEL
  32. help
  33. This option controls verbose debugging information which can be
  34. printed when the kernel detects an internal error. This debugging
  35. information is useful to kernel hackers when tracking down problems,
  36. but mostly meaningless to other people. It's safe to say Y unless
  37. you are concerned with the code size or don't want to see these
  38. messages.
  39. # These options are only for real kernel hackers who want to get their hands dirty.
  40. config DEBUG_LL
  41. bool "Kernel low-level debugging functions"
  42. depends on DEBUG_KERNEL
  43. help
  44. Say Y here to include definitions of printascii, printch, printhex
  45. in the kernel. This is helpful if you are debugging code that
  46. executes before the console is initialized.
  47. config DEBUG_ICEDCC
  48. bool "Kernel low-level debugging via EmbeddedICE DCC channel"
  49. depends on DEBUG_LL
  50. help
  51. Say Y here if you want the debug print routines to direct their
  52. output to the EmbeddedICE macrocell's DCC channel using
  53. co-processor 14. This is known to work on the ARM9 style ICE
  54. channel.
  55. It does include a timeout to ensure that the system does not
  56. totally freeze when there is nothing connected to read.
  57. config DEBUG_DC21285_PORT
  58. bool "Kernel low-level debugging messages via footbridge serial port"
  59. depends on DEBUG_LL && FOOTBRIDGE
  60. help
  61. Say Y here if you want the debug print routines to direct their
  62. output to the serial port in the DC21285 (Footbridge). Saying N
  63. will cause the debug messages to appear on the first 16550
  64. serial port.
  65. config DEBUG_CLPS711X_UART2
  66. bool "Kernel low-level debugging messages via UART2"
  67. depends on DEBUG_LL && ARCH_CLPS711X
  68. help
  69. Say Y here if you want the debug print routines to direct their
  70. output to the second serial port on these devices. Saying N will
  71. cause the debug messages to appear on the first serial port.
  72. config DEBUG_S3C_PORT
  73. depends on DEBUG_LL && PLAT_S3C
  74. bool "Kernel low-level debugging messages via S3C UART"
  75. help
  76. Say Y here if you want debug print routines to go to one of the
  77. S3C internal UARTs. The chosen UART must have been configured
  78. before it is used.
  79. config DEBUG_S3C_UART
  80. depends on PLAT_S3C
  81. int "S3C UART to use for low-level debug"
  82. default "0"
  83. help
  84. Choice for UART for kernel low-level using S3C UARTS,
  85. should be between zero and two. The port must have been
  86. initialised by the boot-loader before use.
  87. The uncompressor code port configuration is now handled
  88. by CONFIG_S3C_LOWLEVEL_UART_PORT.
  89. endmenu