From: Changwoo Min <changwoo@igalia.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: lukasz.luba@arm.com, rafael@kernel.org, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, lenb@kernel.org, pavel@kernel.org,
kernel-dev@igalia.com, linux-pm@vger.kernel.org,
netdev@vger.kernel.org, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for 6.19 4/4] PM: EM: Add dump to get-perf-domains in the EM YNL spec
Date: Tue, 6 Jan 2026 17:25:06 +0900 [thread overview]
Message-ID: <61c00aaf-1920-4f60-93ee-68e25f90218a@igalia.com> (raw)
In-Reply-To: <m2bjj8i9xn.fsf@gmail.com>
Hi Donald,
On 1/5/26 8:19 PM, Donald Hunter wrote:
> Changwoo Min <changwoo@igalia.com> writes:
>
>> Add dump to get-perf-domains, so that a user can fetch either information
>> about a specific performance domain with do or information about all
>> performance domains with dump. The YNL spec, autogenerated files, and
>> the do implementation are updated, and the dump implementation is added.
>>
>> Suggested-by: Donald Hunter <donald.hunter@gmail.com>
>> Signed-off-by: Changwoo Min <changwoo@igalia.com>
>> ---
>> .../netlink/specs/dev-energymodel.yaml | 12 ++++
>> include/uapi/linux/dev_energymodel.h | 3 +-
>> kernel/power/em_netlink.c | 58 +++++++++++++++++--
>> kernel/power/em_netlink_autogen.c | 16 ++++-
>> kernel/power/em_netlink_autogen.h | 2 +
>> 5 files changed, 82 insertions(+), 9 deletions(-)
>>
>> diff --git a/Documentation/netlink/specs/dev-energymodel.yaml b/Documentation/netlink/specs/dev-energymodel.yaml
>> index af8b8f72f722..1843e68faacf 100644
>> --- a/Documentation/netlink/specs/dev-energymodel.yaml
>> +++ b/Documentation/netlink/specs/dev-energymodel.yaml
>> @@ -47,6 +47,11 @@ attribute-sets:
>> doc: >-
>> Information on all the performance domains.
>> attributes:
>> + -
>> + name: perf-domain-id
>> + type: u32
>> + doc: >-
>> + A unique ID number for each performance domain.
>> -
>> name: perf-domain
>> type: nest
>> @@ -136,6 +141,13 @@ operations:
>> attribute-set: perf-domains
>
> I think this can be changed to 'perf-domain' and you could remove
> the 'perf-domains' attribute-set.
>
>> doc: Get the list of information for all performance domains.
>> do:
>> + request:
>> + attributes:
>> + - perf-domain-id
>> + reply:
>> + attributes:
>> + - perf-domain
>
> If you use 'perf-domain' then the reply attributes would be:
>
> reply:
> attributes: &perf-domain-attrs
> - pad
> - perf-domain-id
> - flags
> - cpus
>
>> + dump:
>> reply:
>> attributes:
>> - perf-domain
>
> You can then change the dump reply to be:
>
> dump:
> reply:
> attributes: *perf-domain-attrs
>
> The dump reply for multiple perf domains would then look like this, no
> need for the 'perf-domains' wrapper:
>
> [{'perf-domain-id': ...,
> 'flags': ...,
> 'cpus': [1, 2, 3]},
> {'perf-domain-id': ...,
> 'flags': ...,
> 'cpus': [1, 2, 3]}]
>
Thank you for the suggestion. I will send v2 soon with your suggested
changes.
Regards,
Changwoo Min
next prev parent reply other threads:[~2026-01-06 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 4:01 [PATCH for 6.19 0/4] Revise the EM YNL spec to be clearer Changwoo Min
2025-12-25 4:01 ` [PATCH for 6.19 1/4] PM: EM: Fix yamllint warnings in the EM YNL spec Changwoo Min
2025-12-31 17:20 ` Donald Hunter
2025-12-25 4:01 ` [PATCH for 6.19 2/4] PM: EM: Rename em.yaml to dev-energymodel.yaml Changwoo Min
2026-01-05 11:25 ` Donald Hunter
2025-12-25 4:01 ` [PATCH for 6.19 3/4] PM: EM: Change cpus' type from string to u64 array in the EM YNL spec Changwoo Min
2026-01-05 11:19 ` Donald Hunter
2025-12-25 4:01 ` [PATCH for 6.19 4/4] PM: EM: Add dump to get-perf-domains " Changwoo Min
2026-01-05 11:19 ` Donald Hunter
2026-01-06 8:25 ` Changwoo Min [this message]
2025-12-30 9:44 ` [PATCH for 6.19 0/4] Revise the EM YNL spec to be clearer Lukasz Luba
2025-12-30 12:56 ` Donald Hunter
2026-01-05 18:22 ` Rafael J. Wysocki
2026-01-07 11:52 ` 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=61c00aaf-1920-4f60-93ee-68e25f90218a@igalia.com \
--to=changwoo@igalia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-dev@igalia.com \
--cc=kuba@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=sched-ext@lists.linux.dev \
/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®