linux-kernel - Re: [PATCH v2 2/2] clk: Add trace events for rate requests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20221207214854.74030C433D7@smtp.kernel.org>
Date:   Wed, 07 Dec 2022 13:48:52 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Steven Rostedt <rostedt@...dmis.org>, maxime@...no.tech
Cc:     Maxime Ripard <maxime@...no.tech>, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 2/2] clk: Add trace events for rate requests

Quoting maxime@...no.tech (2022-10-26 06:46:59)
> 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.
> 
> Reviewed-by: Steven Rostedt (Google) <rostedt@...dmis.org>
> Signed-off-by: Maxime Ripard <maxime@...no.tech>
> ---

Applied to clk-next