]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Kernel hacking" |
2 | ||
192ef366 RB |
3 | config TRACE_IRQFLAGS_SUPPORT |
4 | bool | |
5 | default y | |
6 | ||
1da177e4 LT |
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 | |
3763120a RB |
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. | |
1da177e4 LT |
20 | |
21 | config CMDLINE | |
22 | string "Default kernel command string" | |
23 | default "" | |
24 | help | |
3e7f9b82 JA |
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 | |
1da177e4 LT |
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 | ||
9349075a | 40 | config SMTC_IDLE_HOOK_DEBUG |
c68644d3 RB |
41 | bool "Enable additional debug checks before going into CPU idle loop" |
42 | depends on DEBUG_KERNEL && MIPS_MT_SMTC | |
43 | help | |
44 | This option enables Enable additional debug checks before going into | |
45 | CPU idle loop. For details on these checks, see | |
46 | arch/mips/kernel/smtc.c. This debugging option result in significant | |
47 | overhead so should be disabled in production kernels. | |
48 | ||
1da177e4 LT |
49 | config KGDB |
50 | bool "Remote GDB kernel debugging" | |
cc801077 | 51 | depends on DEBUG_KERNEL && SYS_SUPPORTS_KGDB |
1da177e4 LT |
52 | select DEBUG_INFO |
53 | help | |
54 | If you say Y here, it will be possible to remotely debug the MIPS | |
55 | kernel using gdb. This enlarges your kernel image disk size by | |
56 | several megabytes and requires a machine with more than 16 MB, | |
57 | better 32 MB RAM to avoid excessive linking time. This is only | |
58 | useful for kernel hackers. If unsure, say N. | |
59 | ||
cc801077 RB |
60 | config SYS_SUPPORTS_KGDB |
61 | bool | |
62 | ||
1da177e4 LT |
63 | config GDB_CONSOLE |
64 | bool "Console output to GDB" | |
65 | depends on KGDB | |
66 | help | |
67 | If you are using GDB for remote debugging over a serial port and | |
68 | would like kernel messages to be formatted into GDB $O packets so | |
69 | that GDB prints them as program output, say 'Y'. | |
70 | ||
71 | config SB1XXX_CORELIS | |
72 | bool "Corelis Debugger" | |
73 | depends on SIBYTE_SB1xxx_SOC | |
74 | select DEBUG_INFO | |
75 | help | |
76 | Select compile flags that produce code that can be processed by the | |
77 | Corelis mksym utility and UDB Emulator. | |
78 | ||
79 | config RUNTIME_DEBUG | |
80 | bool "Enable run-time debugging" | |
81 | depends on DEBUG_KERNEL | |
82 | help | |
83 | If you say Y here, some debugging macros will do run-time checking. | |
84 | If you say N here, those macros will mostly turn to no-ops. See | |
85 | include/asm-mips/debug.h for debuging macros. | |
86 | If unsure, say N. | |
87 | ||
88 | config MIPS_UNCACHED | |
89 | bool "Run uncached" | |
90 | depends on DEBUG_KERNEL && !SMP && !SGI_IP27 | |
91 | help | |
92 | If you say Y here there kernel will disable all CPU caches. This will | |
93 | reduce the system's performance dramatically but can help finding | |
94 | otherwise hard to track bugs. It can also useful if you're doing | |
95 | hardware debugging with a logic analyzer and need to see all traffic | |
96 | on the bus. | |
97 | ||
98 | endmenu |