From: Changwoo Min <changwoo@igalia.com>
To: lukasz.luba@arm.com, rafael@kernel.org, len.brown@intel.com,
pavel@kernel.org
Cc: christian.loehle@arm.com, tj@kernel.org, kernel-dev@igalia.com,
linux-pm@vger.kernel.org, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org, Changwoo Min <changwoo@igalia.com>
Subject: [PATCH v6 02/10] PM: EM: Expose the ID of a performance domain via debugfs
Date: Tue, 21 Oct 2025 07:09:06 +0900 [thread overview]
Message-ID: <20251020220914.320832-3-changwoo@igalia.com> (raw)
In-Reply-To: <20251020220914.320832-1-changwoo@igalia.com>
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>
Reviewed-by: Lukasz Luba <lukasz.luba@arm.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 2047b546ad11..756debf5406a 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)
--
2.51.1.dirty
next prev parent reply other threads:[~2025-10-20 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 22:09 [PATCH v6 00/10] PM: EM: Add netlink support for the energy model Changwoo Min
2025-10-20 22:09 ` [PATCH v6 01/10] PM: EM: Assign a unique ID when creating a performance domain Changwoo Min
2025-10-20 22:09 ` Changwoo Min [this message]
2025-10-20 22:09 ` [PATCH v6 03/10] PM: EM: Add em.yaml and autogen files Changwoo Min
2025-10-20 22:09 ` [PATCH v6 04/10] PM: EM: Add a skeleton code for netlink notification Changwoo Min
2025-10-20 22:09 ` [PATCH v6 05/10] PM: EM: Add an iterator and accessor for the performance domain Changwoo Min
2025-10-20 22:09 ` [PATCH v6 06/10] PM: EM: Implement em_nl_get_pds_doit() Changwoo Min
2025-10-20 22:09 ` [PATCH v6 07/10] PM: EM: Implement em_nl_get_pd_table_doit() Changwoo Min
2025-10-20 22:09 ` [PATCH v6 08/10] PM: EM: Implement em_notify_pd_deleted() Changwoo Min
2025-10-20 22:09 ` [PATCH v6 09/10] PM: EM: Implement em_notify_pd_created/updated() Changwoo Min
2025-10-20 22:09 ` [PATCH v6 10/10] PM: EM: Notify an event when the performance domain changes Changwoo Min
2025-10-21 17:52 ` [PATCH v6 00/10] PM: EM: Add netlink support for the energy model Rafael J. Wysocki
2025-10-22 13:02 ` 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=20251020220914.320832-3-changwoo@igalia.com \
--to=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=lukasz.luba@arm.com \
--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