* Re: [PATCH v4 0/2] Avoid spurious freezer wakeups
[not found] ` <20230926200238.GB13828@noisy.programming.kicks-ass.net>
@ 2023-09-26 20:56 ` Carlos Llamas
2023-09-26 22:04 ` Elliot Berman
0 siblings, 1 reply; 2+ messages in thread
From: Carlos Llamas @ 2023-09-26 20:56 UTC (permalink / raw)
To: Peter Zijlstra
Cc: Elliot Berman, Ingo Molnar, Rafael J. Wysocki, Pavel Machek,
Thomas Gleixner, kernel, linux-arm-msm, linux-kernel, linux-pm,
Prakash Viswalingam, Greg Kroah-Hartman, stable
On Tue, Sep 26, 2023 at 10:02:38PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 26, 2023 at 04:17:33PM +0000, Carlos Llamas wrote:
> >
> > This issue is hurting the performance of our stable 6.1 releases. Does
> > it make sense to backport these patches into stable branches once they
> > land in mainline? I would assume we want to fix the perf regression
> > there too?
>
> Note that these patches are in tip/sched/core, slated for the next merge
> window.
We can wait, no problem. I just wanted to make sure we also patch stable
if needed. Elliot, would you be able to send a backport of your patches
to stable once they land in mainline on the next merge window?
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
--
Carlos Llamas
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v4 0/2] Avoid spurious freezer wakeups
2023-09-26 20:56 ` [PATCH v4 0/2] Avoid spurious freezer wakeups Carlos Llamas
@ 2023-09-26 22:04 ` Elliot Berman
0 siblings, 0 replies; 2+ messages in thread
From: Elliot Berman @ 2023-09-26 22:04 UTC (permalink / raw)
To: Carlos Llamas, Peter Zijlstra
Cc: Ingo Molnar, Rafael J. Wysocki, Pavel Machek, Thomas Gleixner,
kernel, linux-arm-msm, linux-kernel, linux-pm,
Prakash Viswalingam, Greg Kroah-Hartman, stable
On 9/26/2023 1:56 PM, Carlos Llamas wrote:
> On Tue, Sep 26, 2023 at 10:02:38PM +0200, Peter Zijlstra wrote:
>> On Tue, Sep 26, 2023 at 04:17:33PM +0000, Carlos Llamas wrote:
>>>
>>> This issue is hurting the performance of our stable 6.1 releases. Does
>>> it make sense to backport these patches into stable branches once they
>>> land in mainline? I would assume we want to fix the perf regression
>>> there too?
>>
>> Note that these patches are in tip/sched/core, slated for the next merge
>> window.
>
> We can wait, no problem. I just wanted to make sure we also patch stable
> if needed. Elliot, would you be able to send a backport of your patches
> to stable once they land in mainline on the next merge window?
Yep, happy to send it. There's a trivial conflict to resolve w/older
kernels not having the new guard(...)(...) macros.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: stable@vger.kernel.org
>
> --
> Carlos Llamas
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-09-26 22:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20230908-avoid-spurious-freezer-wakeups-v4-0-6155aa3dafae@quicinc.com>
[not found] ` <ZRMEHb3_0Ku1UuK_@google.com>
[not found] ` <20230926200238.GB13828@noisy.programming.kicks-ass.net>
2023-09-26 20:56 ` [PATCH v4 0/2] Avoid spurious freezer wakeups Carlos Llamas
2023-09-26 22:04 ` Elliot Berman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox