[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240130182654.GD4218@thinkpad>
Date: Tue, 30 Jan 2024 23:56:54 +0530
From: Manivannan Sadhasivam <mani@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Krishna chaitanya chundru <quic_krichai@...cinc.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org, mhi@...ts.linux.dev,
linux-arm-msm@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
quic_vbadigan@...cinc.com, quic_ramkri@...cinc.com,
quic_nitegupt@...cinc.com, quic_skananth@...cinc.com,
quic_parass@...cinc.com
Subject: Re: [PATCH v9] bus: mhi: host: Add tracing support
On Tue, Jan 30, 2024 at 09:22:52AM -0500, Steven Rostedt wrote:
> On Tue, 30 Jan 2024 13:41:52 +0530
> Manivannan Sadhasivam <mani@...nel.org> wrote:
>
> > So same trace will get printed for both mhi_channel_command_start() and
> > mhi_channel_command_end()?
>
> The trace output will also include the tracepoint name. That is, it will
> have the same content but will be preceded with:
>
> mhi_channel_command_start: ...
> mhi_channel_command_end: ...
>
Yes, but the message will be the same:
mhi_channel_command_start: chan%d: Updating state to:
mhi_channel_command_end: chan%d: Updating state to:
Either only one of the trace should be present or the second one should print,
"mhi_channel_command_end: chan%d: Updated state to:"
- Mani
--
மணிவண்ணன் சதாசிவம்
Powered by blists - more mailing lists