public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
	peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
	eric.dumazet@gmail.com, darren@dvhart.com, fweisbec@gmail.com,
	patches@linaro.org
Subject: [PATCH tip/core/rcu 0/6] rcutorture and documentation patches for 3.6
Date: Fri, 15 Jun 2012 11:57:25 -0700	[thread overview]
Message-ID: <20120615185725.GA25163@linux.vnet.ibm.com> (raw)

Hello!

This patch series updates documentation and rcutorture:

1.	Update documentation to allow for the new call_srcu() and
	srcu_barrier() functions.
2.	Fix ordering of the torture_ops list.
3.	Make rcutorture actually test the new srcu_barrier() function.
4.	Fix synchronization of the kthreads testing the various
	rcu_barrier() functions.
5.	Fix an incorrect (and quite confusing) message in rcutorture.
6.	Make rcutorture's fakewriters occasionally invoke the appropriate
	rcu_barrier() function so that we test concurrent rcu_barrier()
	calls.

							Thanx, Paul

 b/Documentation/RCU/checklist.txt  |   39 ++++++++++++++++++-------------------
 b/Documentation/RCU/rcubarrier.txt |    6 +++--
 b/Documentation/RCU/torture.txt    |    9 ++++++++
 b/Documentation/RCU/whatisRCU.txt  |    6 ++---
 b/kernel/rcutorture.c              |    4 +--
 kernel/rcutorture.c                |   32 ++++++++++++++++++++++++------
 6 files changed, 64 insertions(+), 32 deletions(-)


             reply	other threads:[~2012-06-15 18:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 18:57 Paul E. McKenney [this message]
2012-06-15 18:57 ` [PATCH tip/core/rcu 1/6] rcu: Update documentation to cover call_srcu() and srcu_barrier() Paul E. McKenney
2012-06-15 18:57   ` [PATCH tip/core/rcu 2/6] rcu: Rationalize ordering of torture_ops list Paul E. McKenney
2012-06-15 20:21     ` Josh Triplett
2012-06-15 18:57   ` [PATCH tip/core/rcu 3/6] rcu: Test srcu_barrier() from rcutorture test suite Paul E. McKenney
2012-06-15 20:25     ` Josh Triplett
2012-06-15 18:57   ` [PATCH tip/core/rcu 4/6] rcu: Fix bug in rcu_barrier() torture test Paul E. McKenney
2012-06-15 19:44     ` Mathieu Desnoyers
2012-06-15 20:16       ` Paul E. McKenney
2012-06-15 18:57   ` [PATCH tip/core/rcu 5/6] rcu: Fix diagnostic-printk typo in rcutorture Paul E. McKenney
2012-06-15 20:30     ` Josh Triplett
2012-06-15 18:57   ` [PATCH tip/core/rcu 6/6] rcu: Make rcutorture fakewriters invoke rcu_barrier() Paul E. McKenney
2012-06-15 20:37     ` Josh Triplett
2012-06-15 21:19       ` Paul E. McKenney
2012-06-15 21:52         ` Josh Triplett
2012-06-15 23:48           ` Paul E. McKenney
2012-06-15 20:19   ` [PATCH tip/core/rcu 1/6] rcu: Update documentation to cover call_srcu() and srcu_barrier() Josh Triplett
2012-06-15 21:16     ` 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=20120615185725.GA25163@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=darren@dvhart.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=eric.dumazet@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=patches@linaro.org \
    --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