diff options
author | James Hogan <james.hogan@imgtec.com> | 2012-10-09 10:54:32 +0100 |
---|---|---|
committer | James Hogan <james.hogan@imgtec.com> | 2013-03-02 20:09:54 +0000 |
commit | 5633004cc2498ff50a5b88d415d3746ff0c301f2 (patch) | |
tree | b60265906c89e68022b8013e2aa2a19127fe3a24 /arch/metag/Kconfig.debug | |
parent | 79f83c02944ccb3dffbc5852e63e966ea34ed63e (diff) | |
download | linux-5633004cc2498ff50a5b88d415d3746ff0c301f2.tar.gz linux-5633004cc2498ff50a5b88d415d3746ff0c301f2.tar.bz2 linux-5633004cc2498ff50a5b88d415d3746ff0c301f2.zip |
metag: Build infrastructure
Add metag build infrastructure.
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Diffstat (limited to 'arch/metag/Kconfig.debug')
-rw-r--r-- | arch/metag/Kconfig.debug | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/arch/metag/Kconfig.debug b/arch/metag/Kconfig.debug new file mode 100644 index 000000000000..e45bbf6a7a5d --- /dev/null +++ b/arch/metag/Kconfig.debug @@ -0,0 +1,40 @@ +menu "Kernel hacking" + +config TRACE_IRQFLAGS_SUPPORT + bool + default y + +source "lib/Kconfig.debug" + +config DEBUG_STACKOVERFLOW + bool "Check for stack overflows" + depends on DEBUG_KERNEL + help + This option will cause messages to be printed if free stack space + drops below a certain limit. + +config 4KSTACKS + bool "Use 4Kb for kernel stacks instead of 8Kb" + depends on DEBUG_KERNEL + help + If you say Y here the kernel will use a 4Kb stacksize for the + kernel stack attached to each process/thread. This facilitates + running more threads on a system and also reduces the pressure + on the VM subsystem for higher order allocations. This option + will also use IRQ stacks to compensate for the reduced stackspace. + +config METAG_FUNCTION_TRACE + bool "Output Meta real-time trace data for function entry/exit" + help + If you say Y here the kernel will use the Meta hardware trace + unit to output information about function entry and exit that + can be used by a debugger for profiling and call-graphs. + +config METAG_POISON_CATCH_BUFFERS + bool "Poison catch buffer contents on kernel entry" + help + If you say Y here the kernel will write poison data to the + catch buffer registers on kernel entry. This will make any + problem with catch buffer handling much more apparent. + +endmenu |