From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [PATCH 2/2] timers: Fix removed self-IPI on global timer's enqueue in nohz_full
Date: Tue, 2 Apr 2024 09:47:37 -0700 [thread overview]
Message-ID: <3f2597ea-81ba-4498-a0ee-84d7e4e3da59@paulmck-laptop> (raw)
In-Reply-To: <ed13826a-d2d3-4999-8d9e-77dfc6245e1c@paulmck-laptop>
On Mon, Apr 01, 2024 at 05:04:10PM -0700, Paul E. McKenney wrote:
> On Mon, Apr 01, 2024 at 11:56:36PM +0200, Frederic Weisbecker wrote:
> > Le Mon, Apr 01, 2024 at 02:26:25PM -0700, Paul E. McKenney a écrit :
> > > > > _ The RCU CPU Stall report. I strongly suspect the cause is the hrtimer
> > > > > enqueue to an offline CPU. Let's solve that and we'll see if it still
> > > > > triggers.
> > > >
> > > > Sounds like a plan!
> > >
> > > Just checking in on this one. I did reproduce your RCU CPU stall report
> > > and also saw a TREE03 OOM that might (or might not) be related. Please
> > > let me know if hammering TREE03 harder or adding some debug would help.
> > > Otherwise, I will assume that you are getting sufficient bug reports
> > > from your own testing to be getting along with.
> >
> > Hehe, there are a lot indeed :-)
> >
> > So there has been some discussion on CPUSET VS Hotplug, as a problem there
> > is likely the cause of the hrtimer warning you saw, which in turn might
> > be the cause of the RCU stalls.
> >
> > Do you always see the hrtimer warning along the RCU stalls? Because if so, this
> > might help:
> > https://lore.kernel.org/lkml/20240401145858.2656598-1-longman@redhat.com/T/#m1bed4d298715d1a6b8289ed48e9353993c63c896
>
> Not always, but why not give it a shot?
And no failures, though I would need to run much longer for this to
mean much. These were wide-spectrum tests, so my next step will be to
run only TREE03 and TREE07.
Thanx, Paul
next prev parent reply other threads:[~2024-04-02 16:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 23:07 [PATCH 0/2] timers: More fixes Frederic Weisbecker
2024-03-18 23:07 ` [PATCH 1/2] timers/migration: Fix endless timer requeue after idle interrupts Frederic Weisbecker
2024-03-21 11:24 ` [tip: timers/urgent] " tip-bot2 for Frederic Weisbecker
2024-03-18 23:07 ` [PATCH 2/2] timers: Fix removed self-IPI on global timer's enqueue in nohz_full Frederic Weisbecker
2024-03-19 9:18 ` Paul E. McKenney
2024-03-20 11:14 ` Paul E. McKenney
2024-03-20 16:15 ` Frederic Weisbecker
2024-03-20 22:55 ` Paul E. McKenney
2024-03-21 11:42 ` Frederic Weisbecker
2024-03-21 12:47 ` Paul E. McKenney
2024-03-22 11:32 ` Frederic Weisbecker
2024-03-22 13:22 ` for_each_domain()/sched_domain_span() has offline CPUs (was Re: [PATCH 2/2] timers: Fix removed self-IPI on global timer's enqueue in nohz_full) Frederic Weisbecker
2024-03-26 16:46 ` Valentin Schneider
2024-03-27 12:42 ` Frederic Weisbecker
2024-03-27 14:28 ` Valentin Schneider
2024-03-28 14:08 ` Valentin Schneider
2024-03-28 16:58 ` Frederic Weisbecker
2024-03-28 20:31 ` Valentin Schneider
2024-03-27 20:42 ` Thomas Gleixner
2024-03-28 20:39 ` Valentin Schneider
2024-03-29 2:08 ` Tejun Heo
2024-03-29 17:06 ` Waiman Long
2024-04-01 21:26 ` [PATCH 2/2] timers: Fix removed self-IPI on global timer's enqueue in nohz_full Paul E. McKenney
2024-04-01 21:56 ` Frederic Weisbecker
2024-04-02 0:04 ` Paul E. McKenney
2024-04-02 16:47 ` Paul E. McKenney [this message]
2024-04-03 18:05 ` Paul E. McKenney
2024-03-21 11:24 ` [tip: timers/urgent] " tip-bot2 for Frederic Weisbecker
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=3f2597ea-81ba-4498-a0ee-84d7e4e3da59@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 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®