projects / deliverable / linux.git / blame
| 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 | ||
| 9 | config DEBUG_STACKOVERFLOW | |
| 10 | bool "Check for stack overflows" | |
| 11 | depends on DEBUG_KERNEL | |
| 12 | help | |
| 13 | This option will cause messages to be printed if free stack space | |
| 14 | drops below a certain limit. | |
| 15 | ||
| 16 | config 4KSTACKS | |
| 17 | bool "Use 4Kb for kernel stacks instead of 8Kb" | |
| 18 | depends on DEBUG_KERNEL | |
| 19 | help | |
| 20 | If you say Y here the kernel will use a 4Kb stacksize for the | |
| 21 | kernel stack attached to each process/thread. This facilitates | |
| 22 | running more threads on a system and also reduces the pressure | |
| 23 | on the VM subsystem for higher order allocations. This option | |
| 24 | will also use IRQ stacks to compensate for the reduced stackspace. | |
| 25 | ||
| 26 | config METAG_FUNCTION_TRACE | |
| 27 | bool "Output Meta real-time trace data for function entry/exit" | |
| 28 | help | |
| 29 | If you say Y here the kernel will use the Meta hardware trace | |
| 30 | unit to output information about function entry and exit that | |
| 31 | can be used by a debugger for profiling and call-graphs. | |
| 32 | ||
| 33 | config METAG_POISON_CATCH_BUFFERS | |
| 34 | bool "Poison catch buffer contents on kernel entry" | |
| 35 | help | |
| 36 | If you say Y here the kernel will write poison data to the | |
| 37 | catch buffer registers on kernel entry. This will make any | |
| 38 | problem with catch buffer handling much more apparent. | |
| 39 | ||
| 40 | endmenu |