From: Trilok Soni <quic_tsoni@quicinc.com>
To: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Elliot Berman <quic_eberman@quicinc.com>,
"Guru Das Srinagesh" <quic_gurus@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] remoteproc: qcom: Add remoteproc tracing
Date: Fri, 24 Feb 2023 09:17:06 -0800 [thread overview]
Message-ID: <31766494-4952-ab02-d9b1-861e81d9b080@quicinc.com> (raw)
In-Reply-To: <20230224165142.17745-2-quic_gokukris@quicinc.com>
On 2/24/2023 8:51 AM, Gokul krishna Krishnakumar wrote:
> This change adds traces to the following rproc events:
> 1. subdevices events - (STRAT/STOP/CRASH)
> 2. subsystem events - (START/STOP/CRASH)
> 3. RPROC framework events - (Firmware Load/Authentication)
Whenever I see 1/2/3 bullets it probably means different patches? I am
not sure if that applies here, but I don't know why you use numbered
bullets here. Also please describe what is the benefit of these trace
events and how you plan to use it? What kind of debugging scenartio it
will help you.
---Trilok Soni
next prev parent reply other threads:[~2023-02-24 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:51 [PATCH v1 0/1] Add trace events for remoteproc Gokul krishna Krishnakumar
2023-02-24 16:51 ` [PATCH v1 1/1] remoteproc: qcom: Add remoteproc tracing Gokul krishna Krishnakumar
2023-02-24 17:08 ` Elliot Berman
2023-02-24 17:17 ` Trilok Soni [this message]
2023-02-27 20:06 ` Bjorn Andersson
2023-03-03 3:27 ` Gokul Krishna Krishnakumar
2023-02-27 19:36 ` [PATCH v1 0/1] Add trace events for remoteproc Bjorn Andersson
2023-02-27 19:54 ` Gokul Krishna Krishnakumar
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=31766494-4952-ab02-d9b1-861e81d9b080@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_eberman@quicinc.com \
--cc=quic_gokukris@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_sibis@quicinc.com \
/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