rcutorture: Allow kvm-test-1-rcu.sh to pause after build

Parallel rcutorture runs is valuable on large systems, but it is not a
good idea to do (say) five builds in parallel if each build believes it
has the whole system at its disposal, especially if the system is shared.
It is also bad to restrict the build to (say) a single CPU just because
the corresponding rcutorture run uses only a single CPU.  This commit
therefore adds a kvm-test-1-rcu.sh ability to pause after the build
completes, which will allow kvm.sh to do a number of builds serially
(with each build thus having the full system at its disposal), then
allow the rcutorture runs to proceed in parallel.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>

1 files changed, 12 insertions, 0 deletions

diff --git a/tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh b/tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh
index 2cb7facbc86d..c3a396518113 100755
--- a/tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh
+++ b/tools/testing/selftests/rcutorture/bin/kvm-test-1-rcu.sh
@@ -96,11 +96,23 @@ then
         cp $builddir/.config $resdir
         cp $builddir/arch/x86/boot/bzImage $resdir
         parse-build.sh $resdir/Make.out $title
+        if test -f $builddir.wait
+        then
+                mv $builddir.wait $builddir.ready
+        fi
 else
         cp $builddir/Make*.out $resdir
         echo Build failed, not running KVM, see $resdir.
+        if test -f $builddir.wait
+        then
+                mv $builddir.wait $builddir.ready
+        fi
         exit 1
 fi
+while test -f $builddir.ready
+do
+        sleep 1
+done
 minutes=$4
 seconds=$(($minutes * 60))
 qemu_args=$5