[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <affa03ed-f859-4e11-9de2-59702b9d5ea4@arm.com>
Date: Mon, 6 Oct 2025 13:24:33 +0100
From: Lukasz Luba <lukasz.luba@....com>
To: Changwoo Min <changwoo@...lia.com>
Cc: christian.loehle@....com, tj@...nel.org, pavel@...nel.org,
len.brown@...el.com, rafael@...nel.org, kernel-dev@...lia.com,
linux-pm@...r.kernel.org, sched-ext@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v4 01/10] PM: EM: Assign a unique ID when creating
a performance domain
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?
Powered by blists - more mailing lists