Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | menu "Kernel hacking" |
| 2 | |
Ralf Baechle | 192ef36 | 2006-07-07 14:07:18 +0100 | [diff] [blame^] | 3 | config TRACE_IRQFLAGS_SUPPORT |
| 4 | bool |
| 5 | default y |
| 6 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 7 | source "lib/Kconfig.debug" |
| 8 | |
| 9 | config CROSSCOMPILE |
| 10 | bool "Are you using a crosscompiler" |
| 11 | help |
| 12 | Say Y here if you are compiling the kernel on a different |
Ralf Baechle | 3763120 | 2006-04-24 13:08:41 +0100 | [diff] [blame] | 13 | architecture than the one it is intended to run on. This is just a |
| 14 | convenience option which will select the appropriate value for |
| 15 | the CROSS_COMPILE make variable which otherwise has to be passed on |
| 16 | the command line from mips-linux-, mipsel-linux-, mips64-linux- and |
| 17 | mips64el-linux- as appropriate for a particular kernel configuration. |
| 18 | You will have to pass the value for CROSS_COMPILE manually if the |
| 19 | name prefix for your tools is different. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 20 | |
| 21 | config CMDLINE |
| 22 | string "Default kernel command string" |
| 23 | default "" |
| 24 | help |
| 25 | On some platforms, there is currently no way for the boot loader to |
| 26 | pass arguments to the kernel. For these platforms, you can supply |
| 27 | some command-line options at build time by entering them here. In |
| 28 | other cases you can specify kernel args so that you don't have |
| 29 | to set them up in board prom initialization routines. |
| 30 | |
| 31 | config DEBUG_STACK_USAGE |
| 32 | bool "Enable stack utilization instrumentation" |
| 33 | depends on DEBUG_KERNEL |
| 34 | help |
| 35 | Enables the display of the minimum amount of free stack which each |
| 36 | task has ever had available in the sysrq-T and sysrq-P debug output. |
| 37 | |
| 38 | This option will slow down process creation somewhat. |
| 39 | |
| 40 | config KGDB |
| 41 | bool "Remote GDB kernel debugging" |
| 42 | depends on DEBUG_KERNEL |
| 43 | select DEBUG_INFO |
| 44 | help |
| 45 | If you say Y here, it will be possible to remotely debug the MIPS |
| 46 | kernel using gdb. This enlarges your kernel image disk size by |
| 47 | several megabytes and requires a machine with more than 16 MB, |
| 48 | better 32 MB RAM to avoid excessive linking time. This is only |
| 49 | useful for kernel hackers. If unsure, say N. |
| 50 | |
| 51 | config GDB_CONSOLE |
| 52 | bool "Console output to GDB" |
| 53 | depends on KGDB |
| 54 | help |
| 55 | If you are using GDB for remote debugging over a serial port and |
| 56 | would like kernel messages to be formatted into GDB $O packets so |
| 57 | that GDB prints them as program output, say 'Y'. |
| 58 | |
| 59 | config SB1XXX_CORELIS |
| 60 | bool "Corelis Debugger" |
| 61 | depends on SIBYTE_SB1xxx_SOC |
| 62 | select DEBUG_INFO |
| 63 | help |
| 64 | Select compile flags that produce code that can be processed by the |
| 65 | Corelis mksym utility and UDB Emulator. |
| 66 | |
| 67 | config RUNTIME_DEBUG |
| 68 | bool "Enable run-time debugging" |
| 69 | depends on DEBUG_KERNEL |
| 70 | help |
| 71 | If you say Y here, some debugging macros will do run-time checking. |
| 72 | If you say N here, those macros will mostly turn to no-ops. See |
| 73 | include/asm-mips/debug.h for debuging macros. |
| 74 | If unsure, say N. |
| 75 | |
| 76 | config MIPS_UNCACHED |
| 77 | bool "Run uncached" |
| 78 | depends on DEBUG_KERNEL && !SMP && !SGI_IP27 |
| 79 | help |
| 80 | If you say Y here there kernel will disable all CPU caches. This will |
| 81 | reduce the system's performance dramatically but can help finding |
| 82 | otherwise hard to track bugs. It can also useful if you're doing |
| 83 | hardware debugging with a logic analyzer and need to see all traffic |
| 84 | on the bus. |
| 85 | |
| 86 | endmenu |