From: Manivannan Sadhasivam <mani@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Krishna chaitanya chundru <quic_krichai@quicinc.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, quic_vbadigan@quicinc.com,
quic_ramkri@quicinc.com, quic_nitegupt@quicinc.com,
quic_skananth@quicinc.com, quic_parass@quicinc.com
Subject: Re: [PATCH v9] bus: mhi: host: Add tracing support
Date: Tue, 30 Jan 2024 23:56:54 +0530 [thread overview]
Message-ID: <20240130182654.GD4218@thinkpad> (raw)
In-Reply-To: <20240130092252.32801387@gandalf.local.home>
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@kernel.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
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-01-30 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 12:23 [PATCH v9] bus: mhi: host: Add tracing support Krishna chaitanya chundru
2024-01-08 13:22 ` Krishna Chaitanya Chundru
2024-01-25 1:52 ` Krishna Chaitanya Chundru
2024-01-30 8:11 ` Manivannan Sadhasivam
2024-01-30 14:22 ` Steven Rostedt
2024-01-30 18:26 ` Manivannan Sadhasivam [this message]
2024-01-31 1:52 ` Krishna Chaitanya Chundru
2024-01-31 1:50 ` Krishna Chaitanya Chundru
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=20240130182654.GD4218@thinkpad \
--to=mani@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhi@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_parass@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).