From: Keita Morisaki <keyz@google.com>
To: christian.loehle@arm.com
Cc: aarontian@google.com, daniel.lezcano@linaro.org, keyz@google.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, lpieralisi@kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rafael@kernel.org, rostedt@goodmis.org, sudeep.holla@arm.com,
yimingtseng@google.com
Subject: Re: [PATCH v2] cpuidle: psci: Add trace for PSCI domain idle
Date: Wed, 29 Jan 2025 16:51:02 +0800 [thread overview]
Message-ID: <20250129085102.1055165-1-keyz@google.com> (raw)
In-Reply-To: <f697970e-3796-41cb-9904-d61cbedec428@arm.com>
> > Yes, psci_domain_idle_(enter|exit) are not meant to replace cpu_idle nor a
> > variant of it. It's new and different events that provide finer=grained info.
> I mentioned it because it means it doesn't benefit from cpu_idle tooling
> directly, which is slightly odd, but fine with me.
I might not fully understand your comments.
Do you mean that even mentioning cpu_idle in the commit message does not feel
right to you, or utilizing cpu_idle by exposing the determined state instead of
adding new trace events is the right direction?
prev parent reply other threads:[~2025-01-29 8:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 4:01 [PATCH] cpuidle: psci: Add trace for PSCI domain idle Keita Morisaki
2025-01-17 15:51 ` Steven Rostedt
2025-01-18 7:24 ` Keita Morisaki
2025-01-20 1:36 ` [PATCH v2] " Keita Morisaki
2025-01-24 20:28 ` Steven Rostedt
2025-01-25 1:27 ` Keita Morisaki
2025-01-25 1:31 ` [PATCH v3] " Keita Morisaki
2025-01-30 17:36 ` Kevin Hilman
2025-02-02 10:42 ` Keita Morisaki
2025-02-02 10:46 ` [PATCH v4] " Keita Morisaki
2025-02-03 5:32 ` Dhruva Gole
2025-01-27 12:16 ` [PATCH v2] " Christian Loehle
2025-01-28 4:24 ` Keita Morisaki
2025-01-28 11:06 ` Christian Loehle
2025-01-29 8:51 ` Keita Morisaki [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=20250129085102.1055165-1-keyz@google.com \
--to=keyz@google.com \
--cc=aarontian@google.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=yimingtseng@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.