From: Keita Morisaki <keyz@google.com>
To: rostedt@goodmis.org
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, sudeep.holla@arm.com, yimingtseng@google.com
Subject: Re: [PATCH] cpuidle: psci: Add trace for PSCI domain idle
Date: Sat, 18 Jan 2025 15:24:38 +0800 [thread overview]
Message-ID: <20250118072438.3647805-1-keyz@google.com> (raw)
In-Reply-To: <20250117105132.4122940b@gandalf.local.home>
Thank you for the review!
> Why not make that into two different events:
> + trace_psci_domain_idle_enter(dev->cpu, state, s2idle);
> ret = psci_cpu_suspend_enter(state) ? -1 : idx;
> + trace_psci_domain_idle_exit(dev->cpu, state, s2idle);
> Then make the above into a DECLARE_EVENT_CLASS:
> DECLARE_EVENT_CLASS(psci_domain_idle_template,
> TP_PROTO(unsigned int cpu_id, unsigned int state, bool s2idle),
> TP_ARGS(cpu_id, state, s2idle),
> TP_STRUCT__entry(
> __field(u32, cpu_id)
> __field(u32, state)
> __field(bool, s2idle)
> ),
> TP_fast_assign(
> __entry->cpu_id = cpu_id;
> __entry->state = state;
> __entry->s2idle = s2idle;
> ),
> TP_printk("cpu_id=%lu state=0x%lx type=%s, is_s2idle=%s",
> (unsigned long)__entry->cpu_id, (unsigned long)__entry->state,
> (__entry->s2idle)?"yes":"no")
> );
> DEFINE_EVENT(psci_domain_idle_template, psci_domain_idle_enter,
> TP_PROTO(unsigned int cpu_id, unsigned int state, bool s2idle),
> TP_ARGS(cpu_id, state, s2idle),
> );
> DEFINE_EVENT(psci_domain_idle_template, psci_domain_idle_exit,
> TP_PROTO(unsigned int cpu_id, unsigned int state, bool s2idle),
> TP_ARGS(cpu_id, state, s2idle),
> );
Looks good. Let me apply this change in v2.
Thanks,
Keita
next prev parent reply other threads:[~2025-01-18 7:24 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 [this message]
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
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=20250118072438.3647805-1-keyz@google.com \
--to=keyz@google.com \
--cc=aarontian@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).