rcu: Drive PROVE_RCU directly off of PROVE_LOCKING
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 19 Jan 2015 02:01:21 +0000 (18:01 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 26 Feb 2015 20:02:11 +0000 (12:02 -0800)
In the past, it has been useful to enable PROVE_LOCKING without also
enabling PROVE_RCU.  However, experience with PROVE_RCU over the past
few years has demonstrated its usefulness, so this commit makes
PROVE_LOCKING directly imply PROVE_RCU.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
lib/Kconfig.debug

index c5cefb3c009ce9cd51199dc5fef683d7bc9b1bdc..0766672e4c5f0d05af38dc7ef491b410b29bae65 100644 (file)
@@ -1180,16 +1180,7 @@ config DEBUG_CREDENTIALS
 menu "RCU Debugging"
 
 config PROVE_RCU
-       bool "RCU debugging: prove RCU correctness"
-       depends on PROVE_LOCKING
-       default n
-       help
-        This feature enables lockdep extensions that check for correct
-        use of RCU APIs.  This is currently under development.  Say Y
-        if you want to debug RCU usage or help work on the PROVE_RCU
-        feature.
-
-        Say N if you are unsure.
+       def_bool PROVE_LOCKING
 
 config PROVE_RCU_REPEATEDLY
        bool "RCU debugging: don't disable PROVE_RCU on first splat"