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,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/4] Torture-test updates for 4.6
Date: Tue, 23 Feb 2016 21:16:30 -0800 [thread overview]
Message-ID: <20160224051630.GA18874@linux.vnet.ibm.com> (raw)
Hello!
This series provides torture-test updates:
1. Add checks for rcutorture writer starvation.
2. Don't keep empty console.log.diags files.
3. Make rcutorture scripts check for self-detected stalls.
4. Export rcu_gp_is_normal() so that it can be used in torture tests
when run as modules.
Thanx, Paul
------------------------------------------------------------------------
kernel/rcu/update.c | 1 +
tools/testing/selftests/rcutorture/bin/parse-console.sh | 10 ++++++----
2 files changed, 7 insertions(+), 4 deletions(-)
next reply other threads:[~2016-02-24 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 5:16 Paul E. McKenney [this message]
2016-02-24 5:17 ` [PATCH tip/core/rcu 1/4] rcutorture: Add checks for rcutorture writer starvation Paul E. McKenney
2016-02-24 5:17 ` [PATCH tip/core/rcu 2/4] rcutorture: Don't keep empty console.log.diags files Paul E. McKenney
2016-02-24 5:17 ` [PATCH tip/core/rcu 3/4] rcutorture: Check for self-detected stalls Paul E. McKenney
2016-02-24 5:17 ` [PATCH tip/core/rcu 4/4] rcu: Export rcu_gp_is_normal() 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=20160224051630.GA18874@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@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 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.