From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, Valdis.Kletnieks@vt.edu,
dhowells@redhat.com, edumazet@google.com, darren@dvhart.com,
fweisbec@gmail.com, sbw@mit.edu, patches@linaro.org
Subject: Re: [PATCH tip/core/rcu 0/3] Documentation and rcutorture changes for 3.9
Date: Mon, 7 Jan 2013 08:02:25 -0800 [thread overview]
Message-ID: <20130107160225.GD11145@leaf> (raw)
In-Reply-To: <20130105170356.GA13534@linux.vnet.ibm.com>
On Sat, Jan 05, 2013 at 09:03:56AM -0800, Paul E. McKenney wrote:
> Hello!
>
> The following are changes to documentation and rcutorture:
>
> 1. Export trace_clock_local() in order to allow rcutorture event
> tracing to emit the time of the beginning of the RCU read-side
> critical section at the point where a failure is detected.
> 2. Reduce rcutorture's read-side tracing to include only failures,
> thus cutting the number of events down to something reasonable
> (normally zero, in fact!).
> 3. Add atomic_xchg() to the list of atomic operations and memory
> barriers, courtesy of Richard Braun.
For the whole series:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
prev parent reply other threads:[~2013-01-07 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 17:03 [PATCH tip/core/rcu 0/3] Documentation and rcutorture changes for 3.9 Paul E. McKenney
2013-01-05 17:04 ` [PATCH tip/core/rcu 1/3] tracing: Export trace_clock_local() Paul E. McKenney
2013-01-05 17:04 ` [PATCH tip/core/rcu 2/3] rcu: Reduce rcutorture tracing Paul E. McKenney
2013-01-05 17:04 ` [PATCH tip/core/rcu 3/3] Documentation: Memory barrier semantics of atomic_xchg() Paul E. McKenney
2013-01-07 16:02 ` Josh Triplett [this message]
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=20130107160225.GD11145@leaf \
--to=josh@joshtriplett.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--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=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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