[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130507204649.0188E6DB@viggo.jf.intel.com>
Date: Tue, 07 May 2013 13:46:49 -0700
From: Dave Hansen <dave@...1.net>
To: mmarek@...e.cz
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
Dave Hansen <dave@...1.net>
Subject: [PATCH 5/7] group locking debugging options
From: Dave Hansen <dave@...ux.vnet.ibm.com>
There are quite a few of these, and we want to make sure that
there is one-stop-shopping for lock debugging.
Signed-off-by: Dave Hansen <dave@...ux.vnet.ibm.com>
Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>
---
linux.git-davehans/lib/Kconfig.debug | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff -puN lib/Kconfig.debug~order-lock-debugging-options lib/Kconfig.debug
--- linux.git/lib/Kconfig.debug~order-lock-debugging-options 2013-05-07 13:41:38.156522402 -0700
+++ linux.git-davehans/lib/Kconfig.debug 2013-05-07 13:41:38.160522578 -0700
@@ -703,6 +703,8 @@ config DEBUG_PREEMPT
if kernel code uses it in a preemption-unsafe way. Also, the kernel
will detect preemption count underflows.
+menu "Lock Debugging (spinlocks, mutexes, etc...)"
+
config DEBUG_RT_MUTEXES
bool "RT Mutex debugging, deadlock detection"
depends on DEBUG_KERNEL && RT_MUTEXES
@@ -832,12 +834,6 @@ config DEBUG_LOCKDEP
additional runtime checks to debug itself, at the price
of more runtime overhead.
-config TRACE_IRQFLAGS
- bool
- help
- Enables hooks to interrupt enabling and disabling for
- either tracing or lock debugging.
-
config DEBUG_ATOMIC_SLEEP
bool "Sleep inside atomic section checking"
select PREEMPT_COUNT
@@ -859,6 +855,14 @@ config DEBUG_LOCKING_API_SELFTESTS
The following locking APIs are covered: spinlocks, rwlocks,
mutexes and rwsems.
+endmenu # lock debugging
+
+config TRACE_IRQFLAGS
+ bool
+ help
+ Enables hooks to interrupt enabling and disabling for
+ either tracing or lock debugging.
+
config STACKTRACE
bool
depends on STACKTRACE_SUPPORT
_
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists