]>
Commit | Line | Data |
---|---|---|
5633004c JH |
1 | menu "Kernel hacking" |
2 | ||
3 | config TRACE_IRQFLAGS_SUPPORT | |
4 | bool | |
5 | default y | |
6 | ||
7 | source "lib/Kconfig.debug" | |
8 | ||
5633004c JH |
9 | config 4KSTACKS |
10 | bool "Use 4Kb for kernel stacks instead of 8Kb" | |
11 | depends on DEBUG_KERNEL | |
12 | help | |
13 | If you say Y here the kernel will use a 4Kb stacksize for the | |
14 | kernel stack attached to each process/thread. This facilitates | |
15 | running more threads on a system and also reduces the pressure | |
16 | on the VM subsystem for higher order allocations. This option | |
17 | will also use IRQ stacks to compensate for the reduced stackspace. | |
18 | ||
19 | config METAG_FUNCTION_TRACE | |
20 | bool "Output Meta real-time trace data for function entry/exit" | |
21 | help | |
22 | If you say Y here the kernel will use the Meta hardware trace | |
23 | unit to output information about function entry and exit that | |
24 | can be used by a debugger for profiling and call-graphs. | |
25 | ||
26 | config METAG_POISON_CATCH_BUFFERS | |
27 | bool "Poison catch buffer contents on kernel entry" | |
28 | help | |
29 | If you say Y here the kernel will write poison data to the | |
30 | catch buffer registers on kernel entry. This will make any | |
31 | problem with catch buffer handling much more apparent. | |
32 | ||
33 | endmenu |