aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2022-03-18 08:10:18 -0700
committerPaul E. McKenney <paulmck@kernel.org>2022-04-20 16:53:19 -0700
commit58524e0fed6a4509651005c06dc1a4ecb3ed0a61 (patch)
tree3816c52a30f1b9941726705c4ce35731b7dcc302 /tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot
parentrcutorture: Add CONFIG_PREEMPT_DYNAMIC=n to TASKS02 scenario (diff)
downloadlinux-dev-58524e0fed6a4509651005c06dc1a4ecb3ed0a61.tar.xz
linux-dev-58524e0fed6a4509651005c06dc1a4ecb3ed0a61.zip
rcutorture: Allow specifying per-scenario stat_interval
The rcutorture test suite makes double use of the rcutorture.stat_interval module parameter. As its name suggests, it controls the frequency of statistics printing, but it also controls the rcu_torture_writer() stall timeout. The current setting of 15 seconds works surprisingly well. However, given that the RCU tasks stall-warning timeout is ten -minutes-, 15 seconds is too short for TASKS02, which runs a non-preemptible kernel on a single CPU. This commit therefore adds checks for per-scenario specification of the rcutorture.stat_interval module parameter. Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to '')
-rw-r--r--tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot b/tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot
index cd2a188eeb6d..b9b6d67cbc5f 100644
--- a/tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot
+++ b/tools/testing/selftests/rcutorture/configs/rcu/TASKS02.boot
@@ -1 +1,2 @@
rcutorture.torture_type=tasks
+rcutorture.stat_interval=60