From: Peter Zijlstra <peterz@infradead.org>
To: "T.J. Alumbaugh" <talumbau@chromium.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
joel@joelfernandes.org
Subject: Re: sched_core_balance() releasing interrupts with pi_lock held
Date: Tue, 5 Apr 2022 09:48:55 +0200 [thread overview]
Message-ID: <20220405074855.GA30877@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <51b21470-cd72-7ae3-6f33-2dd2e1d6b716@chromium.org>
On Mon, Apr 04, 2022 at 04:17:54PM -0400, T.J. Alumbaugh wrote:
>
> On 3/29/22 17:22, Steven Rostedt wrote:
> > On Mon, 21 Mar 2022 13:30:37 -0400
> > Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > > On Wed, 16 Mar 2022 22:03:41 +0100
> > > Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > > Does something like the below (untested in the extreme) help?
> > > Hi Peter,
> > >
> > > This has been tested extensively by the ChromeOS team and said that it does
> > > appear to fix the problem.
> > >
> > > Could you get this into mainline, and tag it for stable so that it can be
> > > backported to the appropriate stable releases?
> > >
> > > Thanks for the fix!
> > >
> > Hi Peter,
> >
> > I just don't want you to forget about this :-)
> >
> > -- Steve
> >
> Hi Peter,
>
> Just a note that if/when you send this out as a patch, feel free to add:
>
> Tested-by: T.J. Alumbaugh <talumbau@chromium.org>
https://lkml.kernel.org/r/20220330160535.GN8939@worktop.programming.kicks-ass.net
next prev parent reply other threads:[~2022-04-05 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 21:14 sched_core_balance() releasing interrupts with pi_lock held Steven Rostedt
2022-03-15 21:46 ` Steven Rostedt
2022-03-16 16:03 ` Sebastian Andrzej Siewior
2022-03-16 16:18 ` Sebastian Andrzej Siewior
2022-03-16 17:05 ` Sebastian Andrzej Siewior
2022-03-16 20:35 ` Peter Zijlstra
2022-03-17 12:09 ` Sebastian Andrzej Siewior
2022-03-17 14:51 ` [PATCH] sched: Teach the forced-newidle balancer about CPU affinity limitation Sebastian Andrzej Siewior
2022-04-05 8:22 ` [tip: sched/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2022-03-16 20:27 ` sched_core_balance() releasing interrupts with pi_lock held Peter Zijlstra
2022-03-16 21:03 ` Peter Zijlstra
2022-03-21 17:30 ` Steven Rostedt
2022-03-29 21:22 ` Steven Rostedt
2022-04-04 20:17 ` T.J. Alumbaugh
2022-04-05 7:48 ` Peter Zijlstra [this message]
2022-04-05 15:16 ` Dietmar Eggemann
2022-03-17 12:08 ` Sebastian Andrzej Siewior
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=20220405074855.GA30877@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=talumbau@chromium.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