From: Lukasz Luba <lukasz.luba@arm.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: christian.loehle@arm.com, tj@kernel.org, pavel@kernel.org,
kernel-dev@igalia.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, len.brown@intel.com,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v2] PM: EM: Add inotify support when the energy model is updated.
Date: Thu, 22 May 2025 09:43:08 +0100 [thread overview]
Message-ID: <040a0850-a686-42c3-832c-07494cac8ef0@arm.com> (raw)
In-Reply-To: <c85cbb96-8c0f-4f91-a568-20c9de65b10b@igalia.com>
On 5/22/25 09:35, Changwoo Min wrote:
>
>
> On 5/22/25 17:19, Lukasz Luba wrote:
>>
>>
>> On 5/10/25 12:34, Rafael J. Wysocki wrote:
>>> On Sat, May 10, 2025 at 7:07 AM Changwoo Min <changwoo@igalia.com>
>>> wrote:
>
>>>> I am curious about whether the energy mode is likely to be updated more
>>>> often with this change. How often the energy model is likely to be
>>>> updated is the factor to be considered for the interface and the model
>>>> to post-processing the eneergy model (in the BPF schedulers).
>>>
>>> It really is hard to say precisely because eventually this will depend
>>> on the platform firmware. Hopefully, this is not going to happen too
>>> often, but if the thermal envelope of the platform is tight, for
>>> instance, it may not be the case.
>>
>> It's hard to say for all use cases, but there are some easy to measure
>> and understand:
>>
>> 1. Long scenarios with heavy GPU usage (e.g. gaming). Power on CPUs
>> built from High-Performance cells can be affected by +20% and after
>> ~1min
>> 2. Longer recording with heavy ISP usage, similar to above
>>
>> In those two, it's sufficient to update the EM every 1-3sec to reach
>> this +20% after 60sec. Although, at the beginning when the GPU starts
>> heating the updates should happen a bit more often.
>>
>> There are some more complex cases, e.g. when more than 1 Big CPU does
>> heavy computations and the heat is higher than normal EM model of
>> single CPU (even for that scenario profile). Then the updates to EM
>> can go a bit more often (it depends what the platform would like
>> to leverage and achieve w/ SW).
>
> Thank you for the further clarification. I think the netlink
> notification should be fast and efficient enough to cover these scenarios.
Yes, I agree
next prev parent reply other threads:[~2025-05-22 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 1:47 [PATCH v2] PM: EM: Add inotify support when the energy model is updated Changwoo Min
2025-05-07 17:04 ` Tejun Heo
2025-05-08 6:03 ` Changwoo Min
2025-05-09 10:55 ` Lukasz Luba
2025-05-09 16:41 ` Rafael J. Wysocki
2025-05-10 5:07 ` Changwoo Min
2025-05-10 11:34 ` Rafael J. Wysocki
2025-05-22 8:19 ` Lukasz Luba
2025-05-22 8:35 ` Changwoo Min
2025-05-22 8:43 ` Lukasz Luba [this message]
2025-05-10 4:40 ` Changwoo Min
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=040a0850-a686-42c3-832c-07494cac8ef0@arm.com \
--to=lukasz.luba@arm.com \
--cc=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=kernel-dev@igalia.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=tj@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