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
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
linux-stable-mirror@lists.linaro.org
-
Carlos Llamas -
Elliot Berman