From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Christian Loehle <christian.loehle@arm.com>,
Yaxiong Tian <tianyaxiong@kylinos.cn>
Subject: [PATCH v2 0/3] cpufreq: intel_pstate: Adjust the energy model for hybrid systems
Date: Wed, 15 Oct 2025 15:45:28 +0200 [thread overview]
Message-ID: <2404176.ElGaqSPkdT@rafael.j.wysocki> (raw)
Hi Everyone,
This supersedes
https://lore.kernel.org/linux-pm/5937608.DvuYhMxLoT@rafael.j.wysocki/
because the last patch in it resulted from some confusion. Sorry about that.
In this series patch [3/3] simply switches over the energy model callbacks to
using CPU types retrieved from CPUID instead of scaling factors which is more
robust and allows the energy model to be tuned more precisely. In particular,
it will now allow P-cores to be populated when E-cores are utilized above 60%
of their capacity (and not just in the "overutilized" situation or when there
is a task whose utilization exceeds the E-core capacity).
The first two patches in the series are preliminary.
Thanks!
next reply other threads:[~2025-10-15 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 13:45 Rafael J. Wysocki [this message]
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
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=2404176.ElGaqSPkdT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).