|author||Paul E. McKenney <email@example.com>||2011-11-16 17:48:21 -0800|
|committer||Paul E. McKenney <firstname.lastname@example.org>||2011-12-11 10:31:56 -0800|
rcu: Add rcutorture CPU-hotplug capability
Running CPU-hotplug operations concurrently with rcutorture has historically been a good way to find bugs in both RCU and CPU hotplug. This commit therefore adds an rcutorture module parameter called "onoff_interval" that causes a randomly selected CPU-hotplug operation to be executed at the specified interval, in seconds. The default value of "onoff_interval" is zero, which disables rcutorture-instigated CPU-hotplug operations. Signed-off-by: Paul E. McKenney <email@example.com> Signed-off-by: Paul E. McKenney <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/RCU')
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/RCU/torture.txt b/Documentation/RCU/torture.txt
index af40929e1cb0..d67068d0d2b9 100644
@@ -61,6 +61,14 @@ nreaders This is the number of RCU reading threads supported.
To properly exercise RCU implementations with preemptible
read-side critical sections.
+ The number of seconds between each attempt to execute a
+ randomly selected CPU-hotplug operation. Defaults to
+ zero, which disables CPU hotplugging. In HOTPLUG_CPU=n
+ kernels, rcutorture will silently refuse to do any
+ CPU-hotplug operations regardless of what value is
+ specified for onoff_interval.
The number of seconds to keep the test threads affinitied
to a particular subset of the CPUs, defaults to 3 seconds.