From: Lukasz Luba <lukasz.luba@arm.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: christian.loehle@arm.com, tj@kernel.org, pavel@kernel.org,
len.brown@intel.com, rafael@kernel.org, kernel-dev@igalia.com,
linux-pm@vger.kernel.org, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v4 01/10] PM: EM: Assign a unique ID when creating a performance domain
Date: Mon, 6 Oct 2025 13:24:33 +0100 [thread overview]
Message-ID: <affa03ed-f859-4e11-9de2-59702b9d5ea4@arm.com> (raw)
In-Reply-To: <05359260-336f-4047-bc3a-003ace5ad7c4@arm.com>
On 10/6/25 09:17, Lukasz Luba wrote:
> Hi Chanwoo,
>
> My apologies to delay on this topic.
>
> On 9/21/25 04:19, Changwoo Min wrote:
>> It is necessary to refer to a specific performance domain from a
>> userspace. For example, the energy model of a particular performance
>> domain is updated.
>>
>> To this end, assign a unique ID to each performance domain to address it,
>
> Is this related to the sched_ext view on the EM that we cannot re-use
> the allocated ID for the given domain?
Ignore that comment, I know the need now.
Although, there is a small code sneak below...
[..]
>> @@ -660,6 +678,13 @@ int em_dev_register_pd_no_update(struct device
>> *dev, unsigned int nr_states,
>> unlock:
>> mutex_unlock(&em_pd_mutex);
>> + if (_is_cpu_device(dev))
>> + em_check_capacity_update();
>> +
It doesn't below to this $subject at all. It looks like
it was left from some your local changes, isn't it?
next prev parent reply other threads:[~2025-10-06 12:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 3:19 [PATCH RESEND v4 00/10] PM: EM: Add netlink support for the energy model Changwoo Min
2025-09-21 3:19 ` [PATCH RESEND v4 01/10] PM: EM: Assign a unique ID when creating a performance domain Changwoo Min
2025-10-06 8:17 ` Lukasz Luba
2025-10-06 12:24 ` Lukasz Luba [this message]
2025-10-13 13:46 ` Changwoo Min
2025-09-21 3:19 ` [PATCH RESEND v4 02/10] PM: EM: Expose the ID of a performance domain via debugfs Changwoo Min
2025-10-06 14:26 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 03/10] PM: EM: Add an iterator and accessor for the performance domain Changwoo Min
2025-10-06 15:14 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 04/10] PM: EM: Add em.yaml and autogen files Changwoo Min
2025-10-06 15:25 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 05/10] PM: EM: Add a skeleton code for netlink notification Changwoo Min
2025-10-06 15:44 ` Lukasz Luba
2025-10-13 13:46 ` Changwoo Min
2025-10-13 13:53 ` Lukasz Luba
2025-10-13 14:43 ` Changwoo Min
2025-09-21 3:19 ` [PATCH RESEND v4 06/10] PM: EM: Implement em_nl_get_pds_doit() Changwoo Min
2025-10-10 9:32 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 07/10] PM: EM: Implement em_nl_get_pd_table_doit() Changwoo Min
2025-10-10 10:01 ` Lukasz Luba
2025-10-13 13:47 ` Changwoo Min
2025-09-21 3:19 ` [PATCH RESEND v4 08/10] PM: EM: Implement em_notify_pd_deleted() Changwoo Min
2025-10-10 10:17 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 09/10] PM: EM: Implement em_notify_pd_created/updated() Changwoo Min
2025-10-10 10:19 ` Lukasz Luba
2025-09-21 3:19 ` [PATCH RESEND v4 10/10] PM: EM: Notify an event when the performance domain changes Changwoo Min
2025-10-10 10:20 ` 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=affa03ed-f859-4e11-9de2-59702b9d5ea4@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=sched-ext@lists.linux.dev \
--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
all inboxes | Powered by JetHome®