From: Lukasz Luba <lukasz.luba@arm.com>
To: rafael@kernel.org
Cc: dietmar.eggemann@arm.com, Pierre.Gondois@arm.com,
ionela.voinescu@arm.com, viresh.kumar@linaro.org,
daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
mka@chromium.org, nm@ti.com, sboyd@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, cristian.marussi@arm.com,
sudeep.holla@arm.com, matthias.bgg@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][PATCH 0/8] Introduce support for artificial Energy Model
Date: Mon, 4 Apr 2022 13:35:35 +0100 [thread overview]
Message-ID: <76230a1c-73b8-c471-c62e-3ec9b33461a6@arm.com> (raw)
In-Reply-To: <20220321095729.20655-1-lukasz.luba@arm.com>
Hi Rafael,
The patch set has been on LKML for quite a while and got one ACK,
for the code touching something outside the EM (thermal cooling).
AFAICS there is no interest and objections from others for this code.
Therefore, I have a question:
What would be be process to have merge this code?
(We had internally a few reviews of this code)
On 3/21/22 09:57, Lukasz Luba wrote:
> Hi all,
>
> This patch set adds new callback and support for artificial Energy Model (EM).
> The new EMs have artificially generated performance states.
> Such EMs can be created from lean information sources, such
> as the relative energy efficiency between CPUs. The ACPI based
> platforms provide this information
> (ACPI 6.4, s5.2.12.14 'GIC CPU Interface (GICC) Structure'
> 'Processor Power efficiency Class' field).
>
> Artificial EMs might require to directly provide the 'cost' of
> the generated performance state. This patch set adds a new callback
> .get_cost() for this. The EM framework does not force any model
> or formula, it's up to the platform code.
>
> Artificial EMs aim to leverage the Energy Aware Scheduler
> (EAS). Other frameworks relying on performance states
> information (i.e. IPA/DTPM) must be informed of the
> EM type and might be prevented from using it. This patch
> sets also does this by introducing a new flag:
> EM_PERF_DOMAIN_ARTIFICIAL.
>
> The patch set is based on current linux-next, where some
> changes to OPP & EM are queuing.
>
> The patch set also contains (patch 7/8 and patch 8/8) logic which prevents
> two EM's client frameworks from using this new EM type. Some other approach,
> using 'milli-watts', has been proposed and discussed, but refused [1].
> This new flag is more precised and should not leave space for
> wrong interpretation.
>
> Shortly after this patch set you will see a patch set implementing the
> platform code and registering this new EM.
>
No one from Arm is an official maintainer of the EM code.
Regards,
Lukasz
next prev parent reply other threads:[~2022-04-04 12:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 9:57 Lukasz Luba
2022-03-21 9:57 ` [RESEND][PATCH 1/8] PM: EM: Add .get_cost() callback Lukasz Luba
2022-04-04 16:00 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 2/8] PM: EM: Add artificial EM flag Lukasz Luba
2022-04-04 16:01 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 3/8] PM: EM: Use the new .get_cost() callback while registering EM Lukasz Luba
2022-04-04 16:01 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 4/8] PM: EM: Change the order of arguments in the .active_power() callback Lukasz Luba
2022-04-04 16:02 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 5/8] PM: EM: Remove old debugfs files and print all 'flags' Lukasz Luba
2022-04-04 16:02 ` Ionela Voinescu
2022-04-04 16:31 ` Lukasz Luba
2022-03-21 9:57 ` [RESEND][PATCH 6/8] Documentation: EM: Add artificial EM registration description Lukasz Luba
2022-04-04 16:02 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 7/8] thermal: cooling: Check Energy Model type in cpufreq_cooling and devfreq_cooling Lukasz Luba
2022-03-28 3:27 ` Viresh Kumar
2022-03-29 6:37 ` Lukasz Luba
2022-04-04 16:02 ` Ionela Voinescu
2022-03-21 9:57 ` [RESEND][PATCH 8/8] powercap: DTPM: Check for Energy Model type Lukasz Luba
2022-04-04 16:03 ` Ionela Voinescu
2022-04-04 12:35 ` Lukasz Luba [this message]
2022-04-12 6:53 ` [RESEND][PATCH 0/8] Introduce support for artificial Energy Model Lukasz Luba
2022-04-13 14:29 ` Rafael J. Wysocki
2022-04-13 14:47 ` Lukasz Luba
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=76230a1c-73b8-c471-c62e-3ec9b33461a6@arm.com \
--to=lukasz.luba@arm.com \
--cc=Pierre.Gondois@arm.com \
--cc=cristian.marussi@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@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
all inboxes | Powered by JetHome®