From: Greg KH <gregkh@linuxfoundation.org>
To: Qais Yousef <qyousef@layalina.io>
Cc: stable@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Backport unlink misfit patches into 6.1.y
Date: Mon, 21 Aug 2023 15:09:26 +0200 [thread overview]
Message-ID: <2023082118-slot-nutrient-990d@gregkh> (raw)
In-Reply-To: <20230820191650.532978-1-qyousef@layalina.io>
On Sun, Aug 20, 2023 at 08:16:48PM +0100, Qais Yousef wrote:
> Decoupling misfit from overutilized better helps handling misfit due to
> uclamp_min only being misfit without triggering overutilized state, which is
> bad from energy point of view as it prematurely disables energy aware
> scheduling.
>
> The series also makes the search for a better CPU under bad thermal condition
> more comprehensive, which is useful improvement when the system is under bad
> thermal condition.
>
> Backports to 5.10.y and 5.15.y is hard as find_energy_efficient_cpu() is
> different. But it applies cleanly on 6.1.y
>
> Compile tested against various randconfigs for different archs.
>
> Boot tested on android14-6.1 GKI kernel.
>
> Based on v6.1.46
>
> Original series
>
> https://lore.kernel.org/lkml/20230201143628.270912-1-vincent.guittot@linaro.org/
>
> Thanks!
Both now queued up, thanks!
greg k-h
prev parent reply other threads:[~2023-08-21 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 19:16 [PATCH 0/2] Backport unlink misfit patches into 6.1.y Qais Yousef
2023-08-20 19:16 ` [PATCH 1/2] sched/fair: unlink misfit task from cpu overutilized Qais Yousef
2023-08-20 19:16 ` [PATCH 2/2] sched/fair: Remove capacity inversion detection Qais Yousef
2023-08-21 13:09 ` 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=2023082118-slot-nutrient-990d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox