All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
	Uladzislau Rezki <urezki@gmail.com>,
	Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: Re: [PATCH 3/3] rcu/exp: Remove needless CPU up quiescent state report
Date: Fri, 21 Feb 2025 16:31:07 +0100	[thread overview]
Message-ID: <Z7icO5sp9SoXZSJs@localhost.localdomain> (raw)
In-Reply-To: <966fe653-7dbf-40b6-8b6e-c9bcf7b34335@paulmck-laptop>

Le Wed, Feb 19, 2025 at 07:55:05AM -0800, Paul E. McKenney a écrit :
> > > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > > index 86935fe00397..40d6090a33f5 100644
> > > --- a/kernel/rcu/tree.c
> > > +++ b/kernel/rcu/tree.c
> > > @@ -4347,6 +4347,12 @@ void rcutree_report_cpu_dead(void)
> > >  	 * may introduce a new READ-side while it is actually off the QS masks.
> > >  	 */
> > >  	lockdep_assert_irqs_disabled();
> > > +	/*
> > > +	 * CPUHP_AP_SMPCFD_DYING was the last call for rcu_exp_handler() execution.
> > > +	 * The requested QS must have been reported on the last context switch
> > > +	 * from stop machine to idle.
> > > +	 */
> > > +	WARN_ON_ONCE(rdp->cpu_no_qs.b.exp);
> > >  	// Do any dangling deferred wakeups.
> > >  	do_nocb_deferred_wakeup(rdp);
> > 
> > I fired off a 30-minute run of 100*TREE03 with this change also.
> 
> And no failures!

Ok I'm adding that one on my queue.

> 
> 							Thanx, Paul
> 
> > > > 3.	Your ideas here!  ;-)
> > > 
> > > :-)
> > 
> > 							Thanx, Paul

  reply	other threads:[~2025-02-21 15:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 23:25 [PATCH 0/3] rcu/exp updates Frederic Weisbecker
2025-02-13 23:25 ` [PATCH 1/3] rcu/exp: Protect against early QS report Frederic Weisbecker
2025-02-14  9:10   ` Paul E. McKenney
2025-03-13 16:40     ` Frederic Weisbecker
2025-03-13 17:04       ` Paul E. McKenney
2025-02-13 23:25 ` [PATCH 2/3] rcu/exp: Remove confusing needless full barrier on task unblock Frederic Weisbecker
2025-02-25 21:59   ` Joel Fernandes
2025-02-26  0:08     ` Paul E. McKenney
2025-02-26 12:52     ` Frederic Weisbecker
2025-02-26 15:04       ` Paul E. McKenney
2025-02-26 15:26         ` Joel Fernandes
2025-02-26 15:34           ` Frederic Weisbecker
2025-02-13 23:25 ` [PATCH 3/3] rcu/exp: Remove needless CPU up quiescent state report Frederic Weisbecker
2025-02-14  9:01   ` Paul E. McKenney
2025-02-14 12:10     ` Frederic Weisbecker
2025-02-15 10:38       ` Paul E. McKenney
2025-02-15 22:23         ` Frederic Weisbecker
2025-02-19 14:58           ` Paul E. McKenney
2025-02-19 15:55             ` Paul E. McKenney
2025-02-21 15:31               ` Frederic Weisbecker [this message]
2025-02-21 15:52             ` Frederic Weisbecker
2025-02-26  0:00               ` Paul E. McKenney
2025-03-03 20:10   ` Paul E. McKenney
2025-03-14 14:39     ` Frederic Weisbecker
2025-03-18 17:07       ` 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=Z7icO5sp9SoXZSJs@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neeraj.upadhyay@amd.com \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --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 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.