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