diff options
author | Paul E. McKenney <paulmck@linux.ibm.com> | 2019-04-09 14:44:49 -0700 |
---|---|---|
committer | Paul E. McKenney <paulmck@linux.ibm.com> | 2019-05-28 09:06:09 -0700 |
commit | ff3bf92d90d396e51eb78c5ecde11a994ab7a179 (patch) | |
tree | 6ba832a9d6128bf12478f8df3b5710431d2c9668 /tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | |
parent | rcutorture: Fix stutter_wait() return value and freelist checks (diff) | |
download | linux-dev-ff3bf92d90d396e51eb78c5ecde11a994ab7a179.tar.xz linux-dev-ff3bf92d90d396e51eb78c5ecde11a994ab7a179.zip |
torture: Allow inter-stutter interval to be specified
Currently, the inter-stutter interval is the same as the stutter duration,
that is, whatever number of jiffies is passed into torture_stutter_init().
This has worked well for quite some time, but the addition of
forward-progress testing to rcutorture can delay processes for several
seconds, which can triple the time that they are stuttered.
This commit therefore adds a second argument to torture_stutter_init()
that specifies the inter-stutter interval. While locktorture preserves
the current behavior, rcutorture uses the RCU CPU stall warning interval
to provide a wider inter-stutter interval.
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
Diffstat (limited to 'tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh')
0 files changed, 0 insertions, 0 deletions