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 RESEND v4 05/10] PM: EM: Add a skeleton code for netlink notification
Date: Mon, 6 Oct 2025 16:44:10 +0100	[thread overview]
Message-ID: <2be75031-e7a6-44e8-a096-945947d73631@arm.com> (raw)
In-Reply-To: <20250921031928.205869-6-changwoo@igalia.com>



On 9/21/25 04:19, Changwoo Min wrote:
> Add a boilerplate code for netlink notification to register the new
> protocol family. Also, initialize and register the netlink during booting.
> The initialization is called at the postcore level, which is late enough
> after the generic netlink is initialized.
> 
> Finally, update MAINTAINERS to include new files.
> 
> Signed-off-by: Changwoo Min <changwoo@igalia.com>
> ---
>   MAINTAINERS               |  2 +-
>   kernel/power/Makefile     |  5 ++++-
>   kernel/power/em_netlink.c | 35 +++++++++++++++++++++++++++++++++++
>   kernel/power/em_netlink.h | 16 ++++++++++++++++
>   4 files changed, 56 insertions(+), 2 deletions(-)
>   create mode 100644 kernel/power/em_netlink.c
>   create mode 100644 kernel/power/em_netlink.h
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0992029d271d..ba528836eac1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9034,7 +9034,7 @@ F:	include/linux/energy_model.h
>   F:	Documentation/power/energy-model.rst
>   F:	Documentation/netlink/specs/em.yaml
>   F:	include/uapi/linux/energy_model.h
> -F:	kernel/power/em_netlink_autogen.*
> +F:	kernel/power/em_netlink*.*
>   
>   EPAPR HYPERVISOR BYTE CHANNEL DEVICE DRIVER
>   M:	Laurentiu Tudor <laurentiu.tudor@nxp.com>
> diff --git a/kernel/power/Makefile b/kernel/power/Makefile
> index 874ad834dc8d..284a760aade7 100644
> --- a/kernel/power/Makefile
> +++ b/kernel/power/Makefile
> @@ -21,4 +21,7 @@ obj-$(CONFIG_PM_WAKELOCKS)	+= wakelock.o
>   
>   obj-$(CONFIG_MAGIC_SYSRQ)	+= poweroff.o
>   
> -obj-$(CONFIG_ENERGY_MODEL)	+= energy_model.o
> +obj-$(CONFIG_ENERGY_MODEL)	+= em.o
> +em-y				:= energy_model.o
> +em-$(CONFIG_NET)		+= em_netlink_autogen.o em_netlink.o
> +
> diff --git a/kernel/power/em_netlink.c b/kernel/power/em_netlink.c
> new file mode 100644
> index 000000000000..f3fbfeff29a4
> --- /dev/null
> +++ b/kernel/power/em_netlink.c
> @@ -0,0 +1,35 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + *
> + * Generic netlink for energy model.
> + *
> + * Copyright (c) 2025 Valve Corporation.
> + * Author: Changwoo Min <changwoo@igalia.com>
> + */
> +
> +#define pr_fmt(fmt) "energy_model: " fmt
> +
> +#include <linux/energy_model.h>
> +#include <net/sock.h>
> +#include <net/genetlink.h>
> +#include <uapi/linux/energy_model.h>
> +
> +#include "em_netlink.h"
> +#include "em_netlink_autogen.h"
> +
> +int em_nl_get_pds_doit(struct sk_buff *skb, struct genl_info *info)
> +{
> +	return -EOPNOTSUPP;
> +}
> +
> +int em_nl_get_pd_table_doit(struct sk_buff *skb, struct genl_info *info)
> +{
> +	return -EOPNOTSUPP;
> +}
> +
> +static int __init em_netlink_init(void)
> +{
> +	return genl_register_family(&em_nl_family);
> +}
> +postcore_initcall(em_netlink_init);
> +
> diff --git a/kernel/power/em_netlink.h b/kernel/power/em_netlink.h
> new file mode 100644
> index 000000000000..acd186c92d6b
> --- /dev/null
> +++ b/kernel/power/em_netlink.h
> @@ -0,0 +1,16 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + *
> + * Generic netlink for energy model.
> + *
> + * Copyright (c) 2025 Valve Corporation.
> + * Author: Changwoo Min <changwoo@igalia.com>
> + */
> +#ifndef _EM_NETLINK_H
> +#define _EM_NETLINK_H
> +
> +#if defined(CONFIG_ENERGY_MODEL) && defined(CONFIG_NET)
> +#else
> +#endif
> +
> +#endif /* _EM_NETLINK_H */

Actually, those declarations of functions from patch 3/10 can
live in this header. We would avoid creating more local headers
in such case.

Then the patch 3/10 would have to go after this patch when
this header is introduced.

Please ignore the comment in the patch 3/10 and try to
use this header. It is also logically linked to the
notifications, so belongs to such header IMHO.

  reply	other threads:[~2025-10-06 15:43 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 [this message]
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=2be75031-e7a6-44e8-a096-945947d73631@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