]> asedeno.scripts.mit.edu Git - linux.git/commit
torture: Use a single build directory for torture scenarios
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 23 Apr 2018 21:03:00 +0000 (14:03 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 25 Jun 2018 18:30:10 +0000 (11:30 -0700)
commit5bfd7d34fe0905421b42f0091ee9c59d83deef9c
tree19417b6c6e6a0dfb26193aee2de754b370d587bd
parentce397d215ccd07b8ae3f71db689aedb85d56ab40
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>
tools/testing/selftests/rcutorture/bin/configinit.sh
tools/testing/selftests/rcutorture/bin/kvm-build.sh
tools/testing/selftests/rcutorture/bin/kvm-test-1-run.sh
tools/testing/selftests/rcutorture/bin/kvm.sh