All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 5/7] group locking debugging options
Date: Mon, 01 Jul 2013 13:04:47 -0700	[thread overview]
Message-ID: <20130701200447.C1FED10A@viggo.jf.intel.com> (raw)
In-Reply-To: <20130701200440.712D8B4E@viggo.jf.intel.com>


From: Dave Hansen <dave@linux.vnet.ibm.com>

Original posting:

	http://lkml.kernel.org/r/20121214184208.D9E5804D@kernel.stglabs.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@linux.vnet.ibm.com>
Signed-off-by: Dave Hansen <dave.hansen@linux.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-07-01 12:53:21.523532080 -0700
+++ linux.git-davehans/lib/Kconfig.debug	2013-07-01 12:53:21.526532213 -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
_

  parent reply	other threads:[~2013-07-01 20:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 20:04 [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2013-07-01 20:04 ` [PATCH 1/7] consolidate per-arch stack overflow debugging options Dave Hansen
2013-07-01 20:04 ` [PATCH 2/7] order memory debugging Kconfig options Dave Hansen
2013-07-08 16:43   ` Paul E. McKenney
2013-07-01 20:04 ` [PATCH 3/7] consolidate runtime testing configs Dave Hansen
2013-07-01 20:04 ` [PATCH 4/7] consolidate compilation option configs Dave Hansen
2013-07-01 20:04 ` Dave Hansen [this message]
2013-07-01 20:04 ` [PATCH 6/7] kconfig: consolidate printk options Dave Hansen
2013-07-01 20:04 ` [PATCH 7/7] hang and lockup detection menu Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2013-05-07 20:46 [PATCH 0/7] Put "Kernel hacking" Kconfig menu on a diet Dave Hansen
2013-05-07 20:46 ` [PATCH 5/7] group locking debugging options Dave Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130701200447.C1FED10A@viggo.jf.intel.com \
    --to=dave@sr71.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.