[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171103101728.28288-6-sj38.park@gmail.com>
Date: Fri, 3 Nov 2017 19:17:24 +0900
From: SeongJae Park <sj38.park@...il.com>
To: paulmck@...ux.vnet.ibm.com, josh@...htriplett.org,
rostedt@...dmis.org
Cc: shuah@...nel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
SeongJae Park <sj38.park@...il.com>
Subject: [PATCH 5/9] rcutorture/kvm.sh: Support execution from any directory
'kvm.sh' for rcutorture is restricting user to execute it from top of
linux source tree. It is just a subtle restriction, but users using it
for the first time could forget the restriction and be confused.
Moreover, it makes commands a little longer and the long commands could
frustrate debugging people. This commit let users to call the script
from any location.
Signed-off-by: SeongJae Park <sj38.park@...il.com>
---
tools/testing/selftests/rcutorture/bin/kvm.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/rcutorture/bin/kvm.sh b/tools/testing/selftests/rcutorture/bin/kvm.sh
index 36f7f499698f..cd62933e33d7 100755
--- a/tools/testing/selftests/rcutorture/bin/kvm.sh
+++ b/tools/testing/selftests/rcutorture/bin/kvm.sh
@@ -1,8 +1,7 @@
#!/bin/bash
#
# Run a series of 14 tests under KVM. These are not particularly
-# well-selected or well-tuned, but are the current set. Run from the
-# top level of the source tree.
+# well-selected or well-tuned, but are the current set.
#
# Edit the definitions below to set the locations of the various directories,
# as well as the test duration.
@@ -34,6 +33,8 @@ T=/tmp/kvm.sh.$$
trap 'rm -rf $T' 0
mkdir $T
+cd `dirname $scriptname`/../../../../../
+
dur=$((30*60))
dryrun=""
KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
--
2.13.0
Powered by blists - more mailing lists