aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/rcutorture/bin/jitter.sh
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2021-02-10 16:28:44 -0800
committerPaul E. McKenney <paulmck@kernel.org>2021-03-08 14:23:01 -0800
commitb674100e630bf9211d7edce06b5d734b125a74ee (patch)
treea2e147cc07b6148ad67d7e2c2ddc8db9e1e52bb5 /tools/testing/selftests/rcutorture/bin/jitter.sh
parenttorture: Move build/run synchronization files into scenario directories (diff)
downloadlinux-dev-b674100e630bf9211d7edce06b5d734b125a74ee.tar.xz
linux-dev-b674100e630bf9211d7edce06b5d734b125a74ee.zip
torture: Use file-based protocol to mark batch's runs complete
Currently, the script generated by kvm.sh does a "wait" to wait on both the current batch's guest OSes and any jitter.sh scripts. This works, but makes it hard to abstract the jittering so that common code can be used for both local and distributed runs. This commit therefore uses "build.run" files in scenario directories, and these files are removed after the corresponding scenario's guest OS has completed. Note that --build-only runs do not create build.run files because they also do not create guest OSes and do not run any jitter.sh scripts. Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/testing/selftests/rcutorture/bin/jitter.sh')
0 files changed, 0 insertions, 0 deletions