Received-SPF: pass (google.com: domain of linux-kernel+bounces-128389-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 2 Apr 2024 09:47:37 -0700
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
Message-ID: <3f2597ea-81ba-4498-a0ee-84d7e4e3da59@paulmck-laptop>
Reply-To: paulmck@kernel.org
References: <20240318230729.15497-3-frederic@kernel.org>
 <464f6be2-4a72-440d-be53-6a1035d56a4f@paulmck-laptop>
 <1b5752c8-ef32-4ed4-b539-95d507ec99ce@paulmck-laptop>
 <ZfsLtMijRrNZfqh6@localhost.localdomain>
 <6a95b6ac-6681-4492-b155-e30c19bb3341@paulmck-laptop>
 <ZfwdEROGFFmIbkCM@lothringen>
 <bf8689c2-0749-47cb-9535-53cf66e34f5e@paulmck-laptop>
 <797f44f9-701d-4fca-a9f4-d112a7178e7b@paulmck-laptop>
 <ZgstlCZn0l9wSv7H@pavilion.home>
 <ed13826a-d2d3-4999-8d9e-77dfc6245e1c@paulmck-laptop>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
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