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 02/10] PM: EM: Expose the ID of a performance domain via debugfs
Date: Mon, 6 Oct 2025 15:26:21 +0100	[thread overview]
Message-ID: <268414ae-43b2-49e0-9ee5-9c51468a6bb0@arm.com> (raw)
In-Reply-To: <20250921031928.205869-3-changwoo@igalia.com>



On 9/21/25 04:19, Changwoo Min wrote:
> For ease of debugging, let's expose the assigned ID of a performance
> domain through debugfs (e.g., /sys/kernel/debug/energy_model/cpu0/id).
> 
> Signed-off-by: Changwoo Min <changwoo@igalia.com>
> ---
>   kernel/power/energy_model.c | 12 ++++++++++++
>   1 file changed, 12 insertions(+)
> 
> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
> index 3fe562b6230e..8998a7f4910a 100644
> --- a/kernel/power/energy_model.c
> +++ b/kernel/power/energy_model.c
> @@ -126,6 +126,16 @@ static int em_debug_flags_show(struct seq_file *s, void *unused)
>   }
>   DEFINE_SHOW_ATTRIBUTE(em_debug_flags);
>   
> +static int em_debug_id_show(struct seq_file *s, void *unused)
> +{
> +	struct em_perf_domain *pd = s->private;
> +
> +	seq_printf(s, "%d\n", pd->id);
> +
> +	return 0;
> +}
> +DEFINE_SHOW_ATTRIBUTE(em_debug_id);
> +
>   static void em_debug_create_pd(struct device *dev)
>   {
>   	struct em_dbg_info *em_dbg;
> @@ -142,6 +152,8 @@ static void em_debug_create_pd(struct device *dev)
>   	debugfs_create_file("flags", 0444, d, dev->em_pd,
>   			    &em_debug_flags_fops);
>   
> +	debugfs_create_file("id", 0444, d, dev->em_pd, &em_debug_id_fops);
> +
>   	em_dbg = devm_kcalloc(dev, dev->em_pd->nr_perf_states,
>   			      sizeof(*em_dbg), GFP_KERNEL);
>   	if (!em_dbg)

LGTM,

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

  reply	other threads:[~2025-10-06 14:26 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 [this message]
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
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=268414ae-43b2-49e0-9ee5-9c51468a6bb0@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®