From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre Gondois <pierre.gondois@arm.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Lukasz Luba <Lukasz.Luba@arm.com>,
linux-kernel@vger.kernel.org, Qais Yousef <qyousef@layalina.io>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3] sched/fair: Use all little CPUs for CPU-bound workload
Date: Mon, 29 Jul 2024 12:07:25 +0200 [thread overview]
Message-ID: <2024072905-chop-zigzagged-bcd6@gregkh> (raw)
In-Reply-To: <2cbb3467-1b49-4c86-9fad-9c75ce7d9c8f@arm.com>
On Mon, Jul 29, 2024 at 11:50:40AM +0200, Pierre Gondois wrote:
> Hello Sasha,
> Would it be possible to pick this patch for the 6.1 stable branch ?
> Or is there something I should do for this purpose ?
>
> Regards,
> Pierre
>
> On 6/25/24 15:25, Pierre Gondois wrote:
> > Hello stable folk,
> >
> > This patch was merged as:
> > commit 3af7524b1419 ("sched/fair: Use all little CPUs for CPU-bound workloads")
> > into 6.7, improving the following:
> > commit 0b0695f2b34a ("sched/fair: Rework load_balance()")
> >
> > Would it be possible to port it to the 6.1 stable branch ?
> > The patch should apply cleanly by cherry-picking onto v6.1.94,
You also forgot 5.10.y and 5.15.y which need it, I've queued it up for
those as well now, thanks.
greg k-h
prev parent reply other threads:[~2024-07-29 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 9:00 [PATCH v3] sched/fair: Use all little CPUs for CPU-bound workload Pierre Gondois
2023-12-07 17:22 ` Qais Yousef
2023-12-23 16:09 ` [tip: sched/core] sched/fair: Use all little CPUs for CPU-bound workloads tip-bot2 for Pierre Gondois
2024-06-25 13:25 ` [PATCH v3] sched/fair: Use all little CPUs for CPU-bound workload Pierre Gondois
2024-07-29 9:50 ` Pierre Gondois
2024-07-29 10:07 ` Greg KH [this message]
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=2024072905-chop-zigzagged-bcd6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Lukasz.Luba@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.