From: "Paul E. McKenney" <paulmck@kernel.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
Davidlohr Bueso <dave@stgolabs.net>,
Kunwu Chan <kunwu.chan@gmail.com>,
Puranjay Mohan <puranjay@kernel.org>,
rcu@vger.kernel.org
Subject: Re: [PATCH v2 0/7] srcu: NMI-safe atomic SRCU readers, and their irqsave forms
Date: Wed, 11 Nov 2026 11:50:32 -0800 [thread overview]
Message-ID: <5f4c0d2c-5abb-4aa5-9332-dc3da315cc76@paulmck-laptop> (raw)
In-Reply-To: <5edbc292-0004-43b7-9371-c3695afd9128@efficios.com>
On Wed, Nov 11, 2026 at 02:40:36PM -0500, Mathieu Desnoyers wrote:
> On 2026-11-11 14:37, David Woodhouse wrote:
> > On Wed, 2026-11-11 at 14:33 -0500, Mathieu Desnoyers wrote:
> > > On 2026-11-11 14:02, David Woodhouse wrote:
> > > > The latter claim is only true in __srcu_read_lock_fast()/_fast_updown()
> > > > isn't it? Not in the atomic-SRCU. Unless we do something like this on
> > > > top?
> > >
> > > It is true for the atomic readers as well. Without
> > > CONFIG_NEED_SRCU_NMI_SAFE, include/linux/srcu.h defines
> > > __srcu_read_lock_nmisafe() as an inline that calls __srcu_read_lock(),
> > > and the same for unlock. So x86 keeps this_cpu_inc() and smp_mb().
> > > Your diff selects the same functions by hand.
> > >
> > > Only the architectures that select NEED_SRCU_NMI_SAFE get the atomic
> > > increments.
> >
> > You are lost in a twisty maze of helper functions, all alike...
>
> I guess I had the best mentor in that regard! ;-)
I resemble that remark! ;-)
Thanx, Paul
next prev parent reply other threads:[~2026-11-11 19:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 14:59 Mathieu Desnoyers
2026-11-11 14:59 ` [PATCH v2 1/7] srcutiny: Do not call synchronize_rcu() from synchronize_srcu_atomic() Mathieu Desnoyers
2026-11-11 18:35 ` Paul E. McKenney
2026-11-12 3:03 ` KunWu Chan
2026-11-11 14:59 ` [PATCH v2 2/7] srcu: Rule for using synchronize_srcu_atomic() from interrupt handlers Mathieu Desnoyers
2026-11-11 18:54 ` Paul E. McKenney
2026-11-12 3:18 ` KunWu Chan
2026-11-11 14:59 ` [PATCH v2 3/7] srcu: Make atomic SRCU readers NMI-safe Mathieu Desnoyers
2026-11-11 19:55 ` Paul E. McKenney
2026-11-12 9:14 ` KunWu Chan
2026-11-11 14:59 ` [PATCH v2 4/7] srcu: Add irqsave variants of the atomic SRCU readers Mathieu Desnoyers
2026-11-11 19:58 ` Paul E. McKenney
2026-11-11 20:04 ` Paul E. McKenney
2026-11-11 20:13 ` Mathieu Desnoyers
2026-11-12 0:07 ` Paul E. McKenney
2026-11-12 1:32 ` Mathieu Desnoyers
2026-11-12 2:13 ` Paul E. McKenney
2026-11-12 2:50 ` Mathieu Desnoyers
2026-11-12 4:25 ` Paul E. McKenney
2026-11-12 20:08 ` Paul E. McKenney
2026-11-11 14:59 ` [PATCH v2 5/7] rcutorture: Run NMI-safe SRCU readers from NMI Mathieu Desnoyers
2026-11-12 0:39 ` Paul E. McKenney
2026-11-11 14:59 ` [PATCH v2 6/7] rcutorture: Test the irqsave forms of atomic SRCU readers Mathieu Desnoyers
2026-11-12 0:45 ` Paul E. McKenney
2026-11-11 14:59 ` [PATCH v2 7/7] rcutorture: Check an atomic SRCU wait within an RCU reader Mathieu Desnoyers
2026-11-12 0:46 ` Paul E. McKenney
2026-11-11 19:02 ` [PATCH v2 0/7] srcu: NMI-safe atomic SRCU readers, and their irqsave forms David Woodhouse
2026-11-11 19:33 ` Mathieu Desnoyers
2026-11-11 19:35 ` Paul E. McKenney
2026-11-11 19:37 ` David Woodhouse
2026-11-11 19:40 ` Mathieu Desnoyers
2026-11-11 19:50 ` Paul E. McKenney [this message]
2026-11-11 19:34 ` Paul E. McKenney
2026-11-12 1:53 ` David Woodhouse
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=5f4c0d2c-5abb-4aa5-9332-dc3da315cc76@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=boqun@kernel.org \
--cc=dave@stgolabs.net \
--cc=dwmw2@infradead.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=kunwu.chan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=puranjay@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
/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
all inboxes | Powered by JetHome®