public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v5 00/10] PM: EM: Add netlink support for the energy model
Date: Tue, 14 Oct 2025 09:54:41 +0100	[thread overview]
Message-ID: <80611bb8-2ea4-4f6c-9dad-774cb65abcf1@arm.com> (raw)
In-Reply-To: <20251014001055.772422-1-changwoo@igalia.com>



On 10/14/25 01:10, Changwoo Min wrote:
> Addressed all the comments from Lukasz and rebased the code to the head
> of the linus tree.
> 
> There is a need to access the energy model from the userspace. One such
> example is the sched_ext schedulers [1]. The userspace part of the
> sched_ext schedules could feed the (post-processed) energy-model
> information to the BPF part of the scheduler.
> 
> Currently, debugfs is the only way to read the energy model from userspace;
> however, it lacks proper notification mechanisms when a performance domain
> and its associated energy model change.
> 
> This patch set introduces a generic netlink for the energy model, as
> discussed in [2]. It allows a userspace program to read the performance
> domain and its energy model. It notifies the userspace program when a
> performance domain is created or deleted or its energy model is updated
> through a multicast interface.
> 
> Specifically, it supports two commands:
>    - EM_CMD_GET_PDS: Get the list of information for all performance
>      domains.
>    - EM_CMD_GET_PD_TABLE: Get the energy model table of a performance
>      domain.
> 
> Also, it supports three notification events:
>    - EM_CMD_PD_CREATED: When a performance domain is created.
>    - EM_CMD_PD_DELETED: When a performance domain is deleted.
>    - EM_CMD_PD_UPDATED: When the energy model table of a performance domain
>      is updated.
> 
> This can be tested using the tool, tools/net/ynl/pyynl/cli.py, for example,
> with the following commands:
> 
>    $> tools/net/ynl/pyynl/cli.py \
>       --spec Documentation/netlink/specs/em.yaml \
>       --do get-pds
>    $> tools/net/ynl/pyynl/cli.py \
>       --spec Documentation/netlink/specs/em.yaml \
>       --do get-pd-table --json '{"pd-id": 0}'
>    $> tools/net/ynl/pyynl/cli.py \
>       --spec Documentation/netlink/specs/em.yaml \
>       --subscribe event  --sleep 10
> 
> [1] https://lwn.net/Articles/922405/
> [2] https://lore.kernel.org/lkml/a82423bc-8c38-4d57-93da-c4f20011cc92@arm.com/
> [3] https://lore.kernel.org/lkml/202506140306.tuIoz8rN-lkp@intel.com/#t

Thank you Changwoo, it looks good.

The patches can go now into some PM testing branches so we can check the
integration/testing in wider configurations.

Regards,
Lukasz

      parent reply	other threads:[~2025-10-14  8:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  0:10 [PATCH v5 00/10] PM: EM: Add netlink support for the energy model Changwoo Min
2025-10-14  0:10 ` [PATCH v5 01/10] PM: EM: Assign a unique ID when creating a performance domain Changwoo Min
2025-10-14  8:41   ` Lukasz Luba
2025-10-14  0:10 ` [PATCH v5 02/10] PM: EM: Expose the ID of a performance domain via debugfs Changwoo Min
2025-10-14  0:10 ` [PATCH v5 03/10] PM: EM: Add em.yaml and autogen files Changwoo Min
2025-10-14  0:10 ` [PATCH v5 04/10] PM: EM: Add a skeleton code for netlink notification Changwoo Min
2025-10-14  8:43   ` Lukasz Luba
2025-10-14  0:10 ` [PATCH v5 05/10] PM: EM: Add an iterator and accessor for the performance domain Changwoo Min
2025-10-14  8:45   ` Lukasz Luba
2025-10-15  4:49   ` kernel test robot
2025-10-20 17:44     ` Rafael J. Wysocki
2025-10-20 21:35       ` Changwoo Min
2025-10-14  0:10 ` [PATCH v5 06/10] PM: EM: Implement em_nl_get_pds_doit() Changwoo Min
2025-10-14  0:10 ` [PATCH v5 07/10] PM: EM: Implement em_nl_get_pd_table_doit() Changwoo Min
2025-10-14  0:10 ` [PATCH v5 08/10] PM: EM: Implement em_notify_pd_deleted() Changwoo Min
2025-10-14  8:47   ` Lukasz Luba
2025-10-15  4:16   ` kernel test robot
2025-10-20 17:48     ` Rafael J. Wysocki
2025-10-14  0:10 ` [PATCH v5 09/10] PM: EM: Implement em_notify_pd_created/updated() Changwoo Min
2025-10-14  8:48   ` Lukasz Luba
2025-10-14  0:10 ` [PATCH v5 10/10] PM: EM: Notify an event when the performance domain changes Changwoo Min
2025-10-14  8:54 ` Lukasz Luba [this message]

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=80611bb8-2ea4-4f6c-9dad-774cb65abcf1@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