From: Steven Rostedt <rostedt@goodmis.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: Add trace events for rate requests
Date: Tue, 18 Oct 2022 10:24:09 -0400 [thread overview]
Message-ID: <20221018102409.594be3e4@gandalf.local.home> (raw)
In-Reply-To: <20221018-clk-rate-request-tracing-v1-2-6f3aa0b0b9de@cerno.tech>
On Tue, 18 Oct 2022 15:56:42 +0200
Maxime Ripard <maxime@cerno.tech> wrote:
> It is currently fairly difficult to follow what clk_rate_request are
> issued, and how they have been modified once done.
>
> Indeed, there's multiple paths that can be taken, some functions are
> recursive and will just forward the request to its parent, etc.
>
> Adding a lot of debug prints is just not very convenient, so let's add
> trace events for the clock requests, one before they are submitted and
> one after they are returned.
>
> That way we can simply toggle the tracing on without modifying the
> kernel code and without affecting performances or the kernel logs too
> much.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
From a tracing point of view:
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> ---
> drivers/clk/clk.c | 31 +++++++++++++++++++++++++++++++
> include/trace/events/clk.h | 43 +++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 74 insertions(+)
next prev parent reply other threads:[~2022-10-18 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 13:56 [PATCH 0/2] clk: Rate Request Tracing Maxime Ripard
2022-10-18 13:56 ` [PATCH 1/2] clk: Store clk_core for clk_rate_request Maxime Ripard
2022-10-26 0:41 ` Stephen Boyd
2022-10-18 13:56 ` [PATCH 2/2] clk: Add trace events for rate requests Maxime Ripard
2022-10-18 14:24 ` Steven Rostedt [this message]
2022-10-24 16:19 ` Steven Rostedt
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=20221018102409.594be3e4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mhiramat@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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