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/4] SRCU changes for v4.19
Date: Mon, 25 Jun 2018 15:47:34 -0700 [thread overview]
Message-ID: <20180625224734.GA10860@linux.vnet.ibm.com> (raw)
Hello!
This series contains SRCU updates:
1. Fix typos in __call_srcu() comment header.
2. Document that srcu_funnel_gp_start() implies srcu_funnel_exp_start().
3. Add address of the first callback to rcutorture output to allow
this output to show (lack of) forward progress.
4. Introduce srcu_read_{un,}lock_notrace() to avoid lockdep issues
when applying SRCU to tracepoints.
Thanx, Paul
------------------------------------------------------------------------
include/linux/srcu.h | 17 +++++++++++++++++
kernel/rcu/srcutree.c | 26 +++++++++++++++-----------
2 files changed, 32 insertions(+), 11 deletions(-)
next reply other threads:[~2018-06-25 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 22:47 Paul E. McKenney [this message]
2018-06-25 22:47 ` [PATCH tip/core/rcu 1/4] srcu: Fix typos in __call_srcu() header comment Paul E. McKenney
2018-06-25 22:53 ` Randy Dunlap
2018-06-25 23:09 ` Paul E. McKenney
2018-06-25 22:47 ` [PATCH tip/core/rcu 2/4] srcu: Document that srcu_funnel_gp_start() implies srcu_funnel_exp_start() Paul E. McKenney
2018-06-25 22:47 ` [PATCH tip/core/rcu 3/4] srcu: Add address of first callback to rcutorture output Paul E. McKenney
2018-06-25 22:47 ` [PATCH tip/core/rcu 4/4] srcu: Introduce srcu_read_{un,}lock_notrace() 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=20180625224734.GA10860@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 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.