kernel/rcu/Kconfig.debug

1 # SPDX-License-Identifier: GPL-2.0-only
3 # RCU-related debugging configuration options
19 	  false-positive splats, we keep it default disabled but once all
33 	  tests on the RCU infrastructure.  The kernel module may be built
36 	  Say Y here if you want RCU performance tests to be built into
48 	  on the RCU infrastructure.  The kernel module may be built
51 	  Say Y here if you want RCU torture tests to be built into
63 	  Note that PREEMPT_COUNT must be enabled if the preempt-disabled
64 	  and bh-disabled checks are to take effect, and that PREEMPT_RCU
65 	  must be enabled for the RCU-nesting checks to take effect.
78 	  log of failure/close-call rcutorture reader segments with the
88 	bool "Log grace-period numbers for rcutorture failures"
93 	  log of failure/close-call rcutorture reader segments with the
94 	  corresponding grace-period sequence numbers.	This information
98 	  Say Y here if you want grace-period sequence numbers logged.
102 	tristate "Scalability tests for read-side synchronization (RCU and others)"
108 	  useful comparing RCU with various read-side synchronization mechanisms.
109 	  The kernel module may be built after the fact on the running kernel to be
112 	  Say Y here if you want these performance tests built into the kernel.
117 	int "RCU CPU stall timeout in seconds"
128 	int "Expedited RCU CPU stall timeout in milliseconds"
154 	bool "Provide RCU CPU-stall notifiers"
162 	  Enable RCU CPU-stall notifiers, which are invoked just before
163 	  printing the RCU CPU stall warning.  As such, bugs in notifier
169 	  that the whole reason that the RCU CPU stall is happening in
171 	  that you are thinking of acquiring.  In which case, having your
184 	  This option enables additional tracepoints for ftrace-style
194 	  This option provides consistency checks in RCU's handling of
195 	  NO_HZ.  These checks have proven quite helpful in detecting
196 	  bugs in arch-specific NO_HZ code.
209 	  scalability, destroys real-time response, degrades battery
211 	  machines, as in systems with more than about 10 or 20 CPUs.
212 	  But in conjunction with tools like KASAN, it can be helpful
214 	  too-short RCU read-side critical sections.