Merge branch 'fix/usb-audio' into for-linus

[safe/jmp/linux-2.6] / arch / blackfin / Kconfig.debug

diff --git a/arch/blackfin/Kconfig.debug b/arch/blackfin/Kconfig.debug
index f08aea4..5f981d9 100644 (file)
--- a/arch/blackfin/Kconfig.debug
+++ b/arch/blackfin/Kconfig.debug
@@ -2,8 +2,43 @@ menu "Kernel hacking"
 
 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 DEBUG_STACK_USAGE
+       bool "Enable stack utilization instrumentation"
+       depends on DEBUG_KERNEL
+       help
+         Enables the display of the minimum amount of free stack which each
+         task has ever had available in the sysrq-T output.
+
+         This option will slow down process creation somewhat.
+
 config HAVE_ARCH_KGDB
-       def_bool y
+       def_bool y
+
+config KGDB_TESTCASE
+       tristate "KGDB: for test case in expect"
+       default n
+       help
+         This is a kgdb test case for automated testing.
+
+config DEBUG_VERBOSE
+       bool "Verbose fault messages"
+       default y
+       select PRINTK
+       help
+         When a program crashes due to an exception, or the kernel detects
+         an internal error, the kernel can print a not so brief message
+         explaining what the problem was. This debugging information is
+         useful to developers and kernel hackers when tracking down problems,
+         but mostly meaningless to other people. This is always helpful for
+         debugging but serves no purpose on a production system.
+         Most people should say N here.
 
 config DEBUG_MMRS
        bool "Generate Blackfin MMR tree"
@@ -169,11 +204,11 @@ config DEBUG_BFIN_HWTRACE_EXPAND_LEN
          4 for (2^4) 16k, or 4096 entries
 
 config DEBUG_BFIN_NO_KERN_HWTRACE
-       bool "Trace user apps (turn off hwtrace in kernel)"
+       bool "Turn off hwtrace in CPLB handlers"
        depends on DEBUG_BFIN_HWTRACE_ON
-       default n
+       default y
        help
-         Some pieces of the kernel contain a lot of flow changes which can
+         The CPLB error handler contains a lot of flow changes which can
          quickly fill up the hardware trace buffer.  When debugging crashes,
          the hardware trace may indicate that the problem lies in kernel
          space when in reality an application is buggy.