From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: lukasz.luba@arm.com, dietmar.eggemann@arm.com, rafael@kernel.org
Subject: [PATCH v2 0/1] Update Energy Model with performance limits
Date: Tue, 29 Oct 2024 09:43:28 +0000 [thread overview]
Message-ID: <20241029094452.495439-1-lukasz.luba@arm.com> (raw)
Hi all,
This patch set allows to specify in the EM the range of performance levels that
the device is allowed to operate. It will impact EAS decision, especially for
SoCs where CPUs share the voltage & frequency domain with other CPUs or devices
e.g.
- Mid CPUs + Big CPU
- Little CPU + L3 cache in DSU
- some other device + Little CPUs
The minimum allowed frequency will be taken into account while doing EAS task
placement simulation. When the min frequency is higher for the whole domain
and not driven by the CPUs in that PD utilization, than the energy for
computation in that PD will be higher. This patch helps to reflect that higher
cost.
More explanation can be found in my presentation at OSPM2023 [1].
I have shown experiments with Big CPU running high frequency and increasing
the L3 cache frequency (to reduce the latency), but that impacted Little
CPU which are in the same DVFS domain with L3 cache. It had bad impact for
total energy consumed by small tasks placed on Little CPU. The EAS was not
aware about the min frequency&voltage of the Little CPUs and energy estimation
was wrong.
Changelog:
v2:
- added mutex to guard simultaneous updates and make them atomic (Hongyan)
- added Doxygen two new arguments description (Dietmar)
- changed patch header description (Dietmar) and added an example
- dropped the SCMI patch for now, since the notifications are not merged there yet
v1 [2]:
- basic implementation
Regards,
Lukasz Luba
[1] https://www.youtube.com/watch?v=2C-5uikSbtM&list=PL0fKordpLTjKsBOUcZqnzlHShri4YBL1H
[2] https://lore.kernel.org/lkml/20240403162315.1458337-1-lukasz.luba@arm.com/
Lukasz Luba (1):
PM: EM: Add min/max available performance state limits
include/linux/energy_model.h | 24 ++++++++++++++---
kernel/power/energy_model.c | 52 ++++++++++++++++++++++++++++++++++++
2 files changed, 72 insertions(+), 4 deletions(-)
--
2.46.0
next reply other threads:[~2024-10-29 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 9:43 Lukasz Luba [this message]
2024-10-29 9:43 ` [PATCH v2 1/1] PM: EM: Add min/max available performance state limits Lukasz Luba
2024-10-29 18:29 ` Rafael J. Wysocki
2024-10-30 8:48 ` Lukasz Luba
2024-10-30 10:01 ` Lukasz Luba
2024-10-30 11:23 ` Rafael J. Wysocki
2024-10-30 11:34 ` Lukasz Luba
2024-10-30 11:41 ` Rafael J. Wysocki
2024-10-30 11:40 ` Rafael J. Wysocki
2024-10-30 11:50 ` Lukasz Luba
2024-10-30 13:18 ` Rafael J. Wysocki
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=20241029094452.495439-1-lukasz.luba@arm.com \
--to=lukasz.luba@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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