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.opensrc@gmail.com
Subject: [PATCH tip/core/rcu 0/6] Torture-test updates for v4.18
Date: Sun, 22 Apr 2018 20:13:46 -0700 [thread overview]
Message-ID: <20180423031346.GA28371@linux.vnet.ibm.com> (raw)
Hello!
This series contains torture-test updates:
1. Add a script to edit output from failed runs. Running this
script takes your editor through the build errors and the various
problems in the console output, for each such file, first showing
a summary of the errors and then the full output.
2. Code cleanup: Fold parse-torture.sh into parse-console.sh.
3. Output end-of-test state onto the console for rcutorture, which
can help locate cases where RCU is unnecessarily starting new
grace periods. Of course, if you are testing the default RCU
flavor, the kernel probably asked for another grace period,
but it can be useful for the other RCU flavors.
4. Print the above end-of-test state in the rcutorture test
summary provided by the rcutorture scripting.
5. Abbreviate kvm.sh summary lines to avoid line wrap.
6. Make kvm-find-errors.sh find build warnings.
Thanx, Paul
------------------------------------------------------------------------
b/kernel/rcu/rcutorture.c | 8
b/tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | 60 ++++++
b/tools/testing/selftests/rcutorture/bin/kvm-recheck-rcu.sh | 12 -
b/tools/testing/selftests/rcutorture/bin/kvm-recheck.sh | 4
b/tools/testing/selftests/rcutorture/bin/kvm-test-1-run.sh | 1
b/tools/testing/selftests/rcutorture/bin/parse-console.sh | 115 ++++++++++--
tools/testing/selftests/rcutorture/bin/parse-torture.sh | 105 ----------
7 files changed, 176 insertions(+), 129 deletions(-)
next reply other threads:[~2018-04-23 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 3:13 Paul E. McKenney [this message]
2018-04-23 3:14 ` [PATCH tip/core/rcu 1/6] torture: Add a script to edit output from failed runs Paul E. McKenney
2018-04-23 3:14 ` [PATCH tip/core/rcu 2/6] torture: Fold parse-torture.sh into parse-console.sh Paul E. McKenney
2018-04-23 3:14 ` [PATCH tip/core/rcu 3/6] rcutorture: Print end-of-test state Paul E. McKenney
2018-04-23 3:14 ` [PATCH tip/core/rcu 4/6] rcutorture: Print end-of-test state in kvm.sh summary Paul E. McKenney
2018-04-23 3:14 ` [PATCH tip/core/rcu 5/6] rcutorture: Abbreviate kvm.sh summary lines Paul E. McKenney
2018-04-23 3:14 ` [PATCH tip/core/rcu 6/6] torture: Make kvm-find-errors.sh find build warnings 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=20180423031346.GA28371@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.opensrc@gmail.com \
--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