mirror of https://lore.kernel.org/lkml/
 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 RESEND v4 06/10] PM: EM: Implement em_nl_get_pds_doit()
Date: Fri, 10 Oct 2025 10:32:28 +0100	[thread overview]
Message-ID: <716995b1-2d70-4053-a929-2f94e696a025@arm.com> (raw)
In-Reply-To: <20250921031928.205869-7-changwoo@igalia.com>



On 9/21/25 04:19, Changwoo Min wrote:
> When a userspace requests EM_CMD_GET_PDS, the kernel responds with
> information on all performance domains. The message format of the
> response is as follows:
> 
> EM_A_PDS_PD (NLA_NESTED)*
>      EM_A_PD_PD_ID (NLA_U32)
>      EM_A_PD_FLAGS (NLA_U64)
>      EM_A_PD_CPUS (NLA_STRING)
> 
> where EM_A_PDS_PD can be repeated as many times as there are performance
> domains, and EM_A_PD_CPUS is a hexadecimal string representing a CPU
> bitmask.
> 
> Signed-off-by: Changwoo Min <changwoo@igalia.com>
> ---
>   kernel/power/em_netlink.c | 82 ++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 81 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/power/em_netlink.c b/kernel/power/em_netlink.c
> index f3fbfeff29a4..31b27c6fe3c9 100644
> --- a/kernel/power/em_netlink.c
> +++ b/kernel/power/em_netlink.c
> @@ -17,9 +17,89 @@
>   #include "em_netlink.h"
>   #include "em_netlink_autogen.h"
>   
> +#define EM_A_PD_CPUS_LEN		256
> +
> +/*************************** Command encoding ********************************/
> +static int __em_nl_get_pd_size(struct em_perf_domain *pd, void *data)
> +{
> +	char cpus_buf[EM_A_PD_CPUS_LEN];
> +	int *tot_msg_sz = data;
> +	int msg_sz, cpus_sz;
> +
> +	cpus_sz = snprintf(cpus_buf, sizeof(cpus_buf), "%*pb",
> +			   cpumask_pr_args(to_cpumask(pd->cpus)));
> +
> +	msg_sz = nla_total_size(0) +			/* EM_A_PDS_PD */
> +		 nla_total_size(sizeof(u32)) +		/* EM_A_PD_PD_ID */
> +		 nla_total_size_64bit(sizeof(u64)) +	/* EM_A_PD_FLAGS */
> +		 nla_total_size(cpus_sz);		/* EM_A_PD_CPUS */
> +
> +	*tot_msg_sz += nlmsg_total_size(genlmsg_msg_size(msg_sz));
> +	return 0;
> +}
> +
> +static int __em_nl_get_pd(struct em_perf_domain *pd, void *data)
> +{
> +	char cpus_buf[EM_A_PD_CPUS_LEN];
> +	struct sk_buff *msg = data;
> +	struct nlattr *entry;
> +
> +	entry = nla_nest_start(msg, EM_A_PDS_PD);
> +	if (!entry)
> +		goto out_cancel_nest;
> +
> +	if (nla_put_u32(msg, EM_A_PD_PD_ID, pd->id))
> +		goto out_cancel_nest;
> +
> +	if (nla_put_u64_64bit(msg, EM_A_PD_FLAGS, pd->flags, EM_A_PD_PAD))
> +		goto out_cancel_nest;
> +
> +	snprintf(cpus_buf, sizeof(cpus_buf), "%*pb",
> +		 cpumask_pr_args(to_cpumask(pd->cpus)));
> +	if (nla_put_string(msg, EM_A_PD_CPUS, cpus_buf))
> +		goto out_cancel_nest;
> +
> +	nla_nest_end(msg, entry);
> +
> +	return 0;
> +
> +out_cancel_nest:
> +	nla_nest_cancel(msg, entry);
> +
> +	return -EMSGSIZE;
> +}
> +
>   int em_nl_get_pds_doit(struct sk_buff *skb, struct genl_info *info)
>   {
> -	return -EOPNOTSUPP;
> +	struct sk_buff *msg;
> +	void *hdr;
> +	int cmd = info->genlhdr->cmd;
> +	int ret = -EMSGSIZE, msg_sz = 0;
> +
> +	for_each_em_perf_domain(__em_nl_get_pd_size, &msg_sz);
> +
> +	msg = genlmsg_new(msg_sz, GFP_KERNEL);
> +	if (!msg)
> +		return -ENOMEM;
> +
> +	hdr = genlmsg_put_reply(msg, info, &em_nl_family, 0, cmd);
> +	if (!hdr)
> +		goto out_free_msg;
> +
> +	ret = for_each_em_perf_domain(__em_nl_get_pd, msg);
> +	if (ret)
> +		goto out_cancel_msg;
> +
> +	genlmsg_end(msg, hdr);
> +
> +	return genlmsg_reply(msg, info);
> +
> +out_cancel_msg:
> +	genlmsg_cancel(msg, hdr);
> +out_free_msg:
> +	nlmsg_free(msg);
> +
> +	return ret;
>   }
>   
>   int em_nl_get_pd_table_doit(struct sk_buff *skb, struct genl_info *info)

LGTM,

Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>


  reply	other threads:[~2025-10-10  9:32 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
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 [this message]
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=716995b1-2d70-4053-a929-2f94e696a025@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®