From: Joel Fernandes <joelagnelf@nvidia.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Zqiang <qiang.zhang@linux.dev>,
frederic@kernel.org, neeraj.upadhyay@kernel.org,
boqun.feng@gmail.com, urezki@gmail.com, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed()
Date: Wed, 10 Sep 2025 10:36:20 -0400 [thread overview]
Message-ID: <20250910143620.GA561834@joelbox2> (raw)
In-Reply-To: <4c7d977b-7d09-48e0-9a88-bae93fa5e401@paulmck-laptop>
[..]
> > kernel/rcu/srcutiny.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/kernel/rcu/srcutiny.c b/kernel/rcu/srcutiny.c
> > index b52ec45698e8..b2da188133fc 100644
> > --- a/kernel/rcu/srcutiny.c
> > +++ b/kernel/rcu/srcutiny.c
> > @@ -181,10 +181,9 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > {
> > unsigned long cookie;
> >
> > - preempt_disable(); // Needed for PREEMPT_LAZY
> > + lockdep_assert_preemption_disabled();
nit: Do we still want to keep the comment that the expectation of preemption
being disabled is for the LAZY case?
thanks,
- Joel
> > cookie = get_state_synchronize_srcu(ssp);
> > if (ULONG_CMP_GE(READ_ONCE(ssp->srcu_idx_max), cookie)) {
> > - preempt_enable();
> > return;
> > }
> > WRITE_ONCE(ssp->srcu_idx_max, cookie);
> > @@ -194,7 +193,6 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > else if (list_empty(&ssp->srcu_work.entry))
> > list_add(&ssp->srcu_work.entry, &srcu_boot_list);
> > }
> > - preempt_enable();
> > }
> >
> > /*
> > --
> > 2.48.1
> >
next prev parent reply other threads:[~2025-09-10 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:39 [PATCH v2] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed() Zqiang
2025-09-10 13:55 ` Paul E. McKenney
2025-09-10 14:36 ` Joel Fernandes [this message]
2025-09-10 15:52 ` Paul E. McKenney
2025-09-11 0:36 ` Zqiang
2025-09-11 11:37 ` Paul E. McKenney
2025-09-11 11:46 ` Zqiang
2025-09-11 12:06 ` 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=20250910143620.GA561834@joelbox2 \
--to=joelagnelf@nvidia.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).