From: "tip-bot2 for Paul E. McKenney" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: core/rcu] torture: Add "make allmodconfig" to torture.sh
Date: Fri, 12 Feb 2021 12:37:14 -0000 [thread overview]
Message-ID: <161313343427.23325.15950775230003397476.tip-bot2@tip-bot2> (raw)
The following commit has been merged into the core/rcu branch of tip:
Commit-ID: a115a775a8d51c51c8c0b89649646a0e15a4978e
Gitweb: https://git.kernel.org/tip/a115a775a8d51c51c8c0b89649646a0e15a4978e
Author: Paul E. McKenney <paulmck@kernel.org>
AuthorDate: Tue, 24 Nov 2020 11:33:05 -08:00
Committer: Paul E. McKenney <paulmck@kernel.org>
CommitterDate: Wed, 06 Jan 2021 17:03:41 -08:00
torture: Add "make allmodconfig" to torture.sh
This commit adds the ability to do "make allmodconfig" to torture.sh,
given that normal rcutorture runs do not normally catch missing exports.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
tools/testing/selftests/rcutorture/bin/torture.sh | 37 +++++++++++++-
1 file changed, 36 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/rcutorture/bin/torture.sh b/tools/testing/selftests/rcutorture/bin/torture.sh
index 0bd8e84..57f2f31 100755
--- a/tools/testing/selftests/rcutorture/bin/torture.sh
+++ b/tools/testing/selftests/rcutorture/bin/torture.sh
@@ -17,6 +17,9 @@ KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
PATH=${KVM}/bin:$PATH; export PATH
. functions.sh
+TORTURE_ALLOTED_CPUS="`identify_qemu_vcpus`"
+MAKE_ALLOTED_CPUS=$((TORTURE_ALLOTED_CPUS*2))
+
# Default duration and apportionment.
duration_base=10
duration_rcutorture_frac=7
@@ -24,6 +27,7 @@ duration_locktorture_frac=1
duration_scftorture_frac=2
# "yes" or "no" parameters
+do_allmodconfig=yes
do_rcutorture=yes
do_locktorture=yes
do_scftorture=yes
@@ -36,6 +40,7 @@ do_kcsan=no
usage () {
echo "Usage: $scriptname optional arguments:"
echo " --doall"
+ echo " --doallmodconfig / --do-no-allmodconfig"
echo " --do-kasan / --do-no-kasan"
echo " --do-kcsan / --do-no-kcsan"
echo " --do-kvfree / --do-no-kvfree"
@@ -53,6 +58,7 @@ while test $# -gt 0
do
case "$1" in
--doall)
+ do_allmodconfig=yes
do_rcutorture=yes
do_locktorture=yes
do_scftorture=yes
@@ -62,6 +68,14 @@ do
do_kasan=yes
do_kcsan=yes
;;
+ --do-allmodconfig|--do-no-allmodconfig)
+ if test "$1" = --do-allmodconfig
+ then
+ do_allmodconfig=yes
+ else
+ do_allmodconfig=no
+ fi
+ ;;
--do-kasan|--do-no-kasan)
if test "$1" = --do-kasan
then
@@ -95,6 +109,7 @@ do
fi
;;
--do-none)
+ do_allmodconfig=no
do_rcutorture=no
do_locktorture=no
do_scftorture=no
@@ -242,6 +257,26 @@ function torture_set {
fi
}
+# make allmodconfig
+if test "$do_allmodconfig" = "yes"
+then
+ echo " --- allmodconfig:" Start `date` | tee -a $T/log
+ amcdir="tools/testing/selftests/rcutorture/res/$ds/allmodconfig"
+ mkdir -p "$amcdir"
+ make -j$MAKE_ALLOTED_CPUS clean > "$amcdir/Make.out" 2>&1
+ make -j$MAKE_ALLOTED_CPUS allmodconfig > "$amcdir/Make.out" 2>&1
+ make -j$MAKE_ALLOTED_CPUS > "$amcdir/Make.out" 2>&1
+ retcode="$?"
+ echo $retcode > "$amcdir/Make.exitcode"
+ if test "$retcode" == 0
+ then
+ echo "allmodconfig($retcode)" $amcdir >> $T/successes
+ else
+ echo "allmodconfig($retcode)" $amcdir >> $T/failures
+ fi
+fi
+
+# --torture rcu
if test "$do_rcutorture" = "yes"
then
torture_bootargs="rcupdate.rcu_cpu_stall_suppress_at_boot=1 torture.disable_onoff_at_boot rcupdate.rcu_task_stall_timeout=30000"
@@ -320,7 +355,7 @@ exit $ret
# @@@
# RCU CPU stall warnings?
# scftorture warnings?
-# Need a way for the invoker to specify clang.
+# Need a way for the invoker to specify clang. Maybe --kcsan-kmake or some such.
# Work out --configs based on number of available CPUs?
# Need to sense CPUs to size scftorture run. Ditto rcuscale and refscale.
# --kconfig as with --bootargs (Both have overrides.)
reply other threads:[~2021-02-12 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161313343427.23325.15950775230003397476.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.