From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: [PATCH tip/core/rcu 0/5] Pre-gp_seq torture-test changes for v4.19
Date: Mon, 25 Jun 2018 15:57:35 -0700 [thread overview]
Message-ID: <20180625225735.GA11793@linux.vnet.ibm.com> (raw)
Hello!
The following changes to torture-testing come before the infamous ->gp_seq
conversion:
1. Use a single build directory for torture scenarios (currently
there is one directory for each build within a given batch, which
makes no sense given that all of these builds are serialized).
2. Remove obsolete TREE08-T.boot file. Use of the shiny new
"--bootargs rcutree.rcu_fanout_exact=1" makes use of a separate
file unnecesary.
3. Make kvm-find-errors.sh find close calls as well as the usual
hard errors.
4. Make online/offline messages appear only for verbose=2. This
change is necessitated by the ability to make CPU-hotplug operations
happen much more frequently than in the past.
5. Keep old-school dmesg format while Joe Perches is changing the
default format. Later, rcutorture can move to the new format
and at the same time update the analysis scripts. (As opposed
to having the analysis scripts just suddenly break when Joe's
changes hit mainline.)
Thanx, Paul
------------------------------------------------------------------------
b/include/linux/torture.h | 2
b/kernel/locking/locktorture.c | 5 +-
b/kernel/rcu/rcuperf.c | 5 +-
b/kernel/rcu/rcutorture.c | 5 +-
b/kernel/torture.c | 15 +++---
b/tools/testing/selftests/rcutorture/bin/configinit.sh | 26 +++++------
b/tools/testing/selftests/rcutorture/bin/kvm-build.sh | 11 ++--
b/tools/testing/selftests/rcutorture/bin/kvm-recheck-rcu.sh | 1
b/tools/testing/selftests/rcutorture/bin/kvm-recheck.sh | 1
b/tools/testing/selftests/rcutorture/bin/kvm-test-1-run.sh | 5 +-
b/tools/testing/selftests/rcutorture/bin/kvm.sh | 2
b/tools/testing/selftests/rcutorture/bin/parse-console.sh | 7 ++
tools/testing/selftests/rcutorture/configs/rcu/TREE08-T.boot | 1
13 files changed, 53 insertions(+), 33 deletions(-)
next reply other threads:[~2018-06-25 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 22:57 Paul E. McKenney [this message]
2018-06-25 22:57 ` [PATCH tip/core/rcu 1/5] torture: Use a single build directory for torture scenarios Paul E. McKenney
2018-06-25 22:57 ` [PATCH tip/core/rcu 2/5] rcutorture: Remove obsolete TREE08-T.boot file Paul E. McKenney
2018-06-25 22:57 ` [PATCH tip/core/rcu 3/5] rcutorture: Make kvm-find-errors.sh find close calls Paul E. McKenney
2018-06-25 22:57 ` [PATCH tip/core/rcu 4/5] torture: Make online/offline messages appear only for verbose=2 Paul E. McKenney
2018-06-25 22:57 ` [PATCH tip/core/rcu 5/5] torture: Keep old-school dmesg format Paul E. McKenney
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=20180625225735.GA11793@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox