From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Christian Loehle <christian.loehle@arm.com>
Cc: Yaxiong Tian <tianyaxiong@kylinos.cn>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, srinivas.pandruvada@linux.intel.com
Subject: Re: [PATCH v2 3/3] cpufreq: intel_pstate: hybrid: Adjust energy model rules
Date: Thu, 16 Oct 2025 15:59:09 +0200 [thread overview]
Message-ID: <1592aa65-9dfb-47d6-9bcf-17afd3184a0a@arm.com> (raw)
In-Reply-To: <CAJZ5v0gyGsTdJ+up-peX5_ggF-YKPep1j0uG6zRGn9UKiHA-KQ@mail.gmail.com>
On 16.10.25 11:52, Rafael J. Wysocki wrote:
> On Thu, Oct 16, 2025 at 11:00 AM Christian Loehle
> <christian.loehle@arm.com> wrote:
>>
>> On 10/16/25 08:48, Yaxiong Tian wrote:
>>> 在 2025/10/15 21:48, Rafael J. Wysocki 写道:> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
[...]
>>> Hi Rafael J. Wysocki:
>>>
>>> Is the increment of this cost for different types of CPUs by one instead
>>> of two?
>>>
>>> cost by increment of 2:
>>> 0~40% 40%~60% 60%~80% 80%~100
>>> LPE-core 2 3 4 5
>>> E-core 4 5 6 7
>>> P-core 6 7 8 9
>>>
>>> So, tasks only start being allocated to more powerful CPUs when
>>> utilization exceeds 80%, but by that point the system is already in an
>>> overloaded state.
>>>
>>> cost by increment of 1:
>>> 0~40% 40%~60% 60%~80% 80%~100
>>> LPE-core 2 3 4 5
>>> E-core 3 4 5 6
>>> P-core 4 5 6 7
>>>
>>> This situation aligns with the description in your patch.
>>>
>>> The idea of this patch looks good to me.
>>
>> Agreed if you want the threshold to be 60% for both it should be +1 for l3
>> and +2 for P-core.
>> Good catch!
>
> OK, I'll send an update of this patch then, but I won't resend the
> first two patches in the series. I don't think that they are
> objectionable.
FWIW: LGTM: tested on i7-13700K (nosmt):
$ cat /sys/devices/system/cpu/cpu{0,8,16}/cpu_capacity
1009
1024
623
root@gulliver:~# cat /sys/kernel/debug/energy_model/cpu0/ps:*/cost
6
7
8
9
root@gulliver:~# cat /sys/kernel/debug/energy_model/cpu8/ps:*/cost
6
7
8
9
root@gulliver:~# cat /sys/kernel/debug/energy_model/cpu16/ps:*/cost
4
5
6
7
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
next prev parent reply other threads:[~2025-10-16 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 13:45 [PATCH v2 0/3] cpufreq: intel_pstate: Adjust the energy model for hybrid systems Rafael J. Wysocki
2025-10-15 13:46 ` [PATCH v2 1/3] cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() Rafael J. Wysocki
2025-10-15 13:47 ` [PATCH v2 2/3] cpufreq: intel_pstate: Add and use hybrid_has_l3() Rafael J. Wysocki
2025-10-15 13:48 ` [PATCH v2 3/3] cpufreq: intel_pstate: hybrid: Adjust energy model rules Rafael J. Wysocki
2025-10-15 15:13 ` Christian Loehle
2025-10-15 15:16 ` Rafael J. Wysocki
2025-10-16 7:48 ` Yaxiong Tian
2025-10-16 9:00 ` Christian Loehle
2025-10-16 9:52 ` Rafael J. Wysocki
2025-10-16 13:59 ` Dietmar Eggemann [this message]
2025-10-16 16:22 ` [PATCH v3 " Rafael J. Wysocki
2025-10-17 1:15 ` Yaxiong Tian
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=1592aa65-9dfb-47d6-9bcf-17afd3184a0a@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=christian.loehle@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tianyaxiong@kylinos.cn \
/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
all inboxes | Powered by JetHome®