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