summaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/rcutorture/bin/kvm.sh
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-04-23 14:03:00 -0700
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-06-25 11:30:10 -0700
commit5bfd7d34fe0905421b42f0091ee9c59d83deef9c (patch)
tree19417b6c6e6a0dfb26193aee2de754b370d587bd /tools/testing/selftests/rcutorture/bin/kvm.sh
parentce397d215ccd07b8ae3f71db689aedb85d56ab40 (diff)
downloadlinux-stable-5bfd7d34fe0905421b42f0091ee9c59d83deef9c.tar.gz
linux-stable-5bfd7d34fe0905421b42f0091ee9c59d83deef9c.tar.bz2
linux-stable-5bfd7d34fe0905421b42f0091ee9c59d83deef9c.zip
torture: Use a single build directory for torture scenarios
The torture scripting currently builds each kernel from a set of parallel runs in its own build directory. This can waste quite a bit of space when running large numbers of concurrent scenarios, and pointlessly given that the builds are run sequentially (albeit with a largish -j number passed to "make"). This commit therefore places all build-command output in the results directory, then does all builds in a single "b1" build directory. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/testing/selftests/rcutorture/bin/kvm.sh')
-rwxr-xr-xtools/testing/selftests/rcutorture/bin/kvm.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/rcutorture/bin/kvm.sh b/tools/testing/selftests/rcutorture/bin/kvm.sh
index 56610dbbdf73..5a7a62d76a50 100755
--- a/tools/testing/selftests/rcutorture/bin/kvm.sh
+++ b/tools/testing/selftests/rcutorture/bin/kvm.sh
@@ -347,7 +347,7 @@ function dump(first, pastlast, batchnum)
print "needqemurun="
jn=1
for (j = first; j < pastlast; j++) {
- builddir=KVM "/b" jn
+ builddir=KVM "/b1"
cpusr[jn] = cpus[j];
if (cfrep[cf[j]] == "") {
cfr[jn] = cf[j];