summaryrefslogtreecommitdiff
path: root/kernel/rcu/Kconfig.debug
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2020-09-03 09:47:42 -0700
committerPaul E. McKenney <paulmck@kernel.org>2020-09-03 09:47:42 -0700
commit7fbe67e46aab13f99d551ab04a1168a7d58cdae9 (patch)
tree8feb62912b645adcc5bccaadb0b81d0674430c3d /kernel/rcu/Kconfig.debug
parentf511ce1424e5f3c32619eb0258afa8abd38fe3cc (diff)
parentcfeac3977ab4b6222a01f79997739d2367a8cc94 (diff)
Merge branch 'strictgp.2020.08.24a' into HEAD
strictgp.2020.08.24a: Strict grace periods for KASAN testing.
Diffstat (limited to 'kernel/rcu/Kconfig.debug')
-rw-r--r--kernel/rcu/Kconfig.debug15
1 files changed, 15 insertions, 0 deletions
diff --git a/kernel/rcu/Kconfig.debug b/kernel/rcu/Kconfig.debug
index 5cb175df6ece..1942c1f1bb65 100644
--- a/kernel/rcu/Kconfig.debug
+++ b/kernel/rcu/Kconfig.debug
@@ -114,4 +114,19 @@ config RCU_EQS_DEBUG
Say N here if you need ultimate kernel/user switch latencies
Say Y if you are unsure
+config RCU_STRICT_GRACE_PERIOD
+ bool "Provide debug RCU implementation with short grace periods"
+ depends on DEBUG_KERNEL && RCU_EXPERT
+ default n
+ select PREEMPT_COUNT if PREEMPT=n
+ help
+ Select this option to build an RCU variant that is strict about
+ grace periods, making them as short as it can. This limits
+ scalability, destroys real-time response, degrades battery
+ lifetime and kills performance. Don't try this on large
+ machines, as in systems with more than about 10 or 20 CPUs.
+ But in conjunction with tools like KASAN, it can be helpful
+ when looking for certain types of RCU usage bugs, for example,
+ too-short RCU read-side critical sections.
+
endmenu # "RCU Debugging"