From: Steven Rostedt <rostedt@goodmis.org>
To: Kajetan Puchalski <kajetan.puchalski@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
lukasz.luba@arm.com, Dietmar.Eggemann@arm.com
Subject: Re: [PATCH] cpuidle: Add cpu_idle_miss trace event
Date: Tue, 26 Jul 2022 10:08:16 -0400 [thread overview]
Message-ID: <20220726100816.3e37ed97@gandalf.local.home> (raw)
In-Reply-To: <Yt/AxPFi88neW7W5@e126311.manchester.arm.com>
On Tue, 26 Jul 2022 11:24:04 +0100
Kajetan Puchalski <kajetan.puchalski@arm.com> wrote:
> --- a/include/trace/events/power.h
> +++ b/include/trace/events/power.h
> @@ -40,6 +40,28 @@ DEFINE_EVENT(cpu, cpu_idle,
> TP_ARGS(state, cpu_id)
> );
>
> +TRACE_EVENT(cpu_idle_miss,
> +
> + TP_PROTO(unsigned int cpu_id, unsigned int state, bool below),
> +
> + TP_ARGS(cpu_id, state, below),
> +
> + TP_STRUCT__entry(
> + __field(u32, cpu_id)
> + __field(u32, state)
> + __field(bool, below)
> + ),
> +
> + TP_fast_assign(
> + __entry->cpu_id = cpu_id;
> + __entry->state = state;
> + __entry->below = below;
> + ),
> +
> + TP_printk("cpu_id=%lu state=%lu type=%s", (unsigned long)__entry->cpu_id,
> + (unsigned long)__entry->state, (__entry->below)?"below":"above")
> +);
> +
> TRACE_EVENT(powernv_throttle,
>
> TP_PROTO(int chip_id, const char *reason, int pmax),
For the tracing POV,
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2022-07-26 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 10:24 Kajetan Puchalski
2022-07-26 14:08 ` Steven Rostedt [this message]
2022-07-26 15:59 ` Kajetan Puchalski
2022-07-29 14:57 ` Rafael J. Wysocki
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=20220726100816.3e37ed97@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Dietmar.Eggemann@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=kajetan.puchalski@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=rafael@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®