From: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
To: <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
<linux-kernel@vger.kernel.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
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>,
Melody Olvera <quic_molvera@quicinc.com>,
Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>
Subject: [PATCH v5 0/2] Patches for introducing traces in remoteproc.
Date: Mon, 12 Jun 2023 15:03:24 -0700 [thread overview]
Message-ID: <cover.1686606835.git.quic_gokukris@quicinc.com> (raw)
V5: Add more text to Kconfig
Move this trace point to function rproc_load_segments() and rename
it to trace_rproc_load_segment_event()
V4: Add config symbol REMOTEPROC_TRACEPOINTS to enable traces
Rename rproc_qcom.h to remoteproc_tracepoints.h
Rename qcom_tracepoints.c to remoteproc_tracepoints.c
Switch to EXPORT_SYMBOL_GPL
V3: Split the Patch to 2 as per suggestion from Mukesh, fixed format
error from v2.
V2: Moved the traces to common code from the qcom_pas driver as per
Bjorns review, fixed text as per Triloks suggestion, Updated QuiC
copyright to 2023.
[1]: https://lore.kernel.org/all/20230224165142.17745-2-quic_gokukris@quicinc.com/
Gokul krishna Krishnakumar (2):
remoteproc: Introduce traces for remoteproc events
remoteproc: qcom: Add remoteproc tracing
drivers/remoteproc/Kconfig | 9 ++
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/qcom_common.c | 37 +++++
drivers/remoteproc/qcom_q6v5.c | 9 ++
drivers/remoteproc/remoteproc_core.c | 5 +
drivers/remoteproc/remoteproc_internal.h | 9 +-
drivers/remoteproc/remoteproc_tracepoints.c | 14 ++
include/trace/events/remoteproc_tracepoints.h | 152 ++++++++++++++++++
8 files changed, 234 insertions(+), 2 deletions(-)
create mode 100644 drivers/remoteproc/remoteproc_tracepoints.c
create mode 100644 include/trace/events/remoteproc_tracepoints.h
base-commit: 1ca04f21b204e99dd704146231adfb79ea2fb366
--
2.40.1
next reply other threads:[~2023-06-12 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 22:03 Gokul krishna Krishnakumar [this message]
2023-06-12 22:03 ` [PATCH v5 1/2] remoteproc: Introduce traces for remoteproc events Gokul krishna Krishnakumar
2023-06-12 22:03 ` [PATCH v5 2/2] remoteproc: qcom: Add remoteproc tracing Gokul krishna Krishnakumar
2023-06-13 6:08 ` kernel test robot
2023-06-13 6:19 ` kernel test robot
2023-06-13 7:42 ` kernel test robot
2023-06-13 15:28 ` 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=cover.1686606835.git.quic_gokukris@quicinc.com \
--to=quic_gokukris@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.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=quic_eberman@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=quic_tsoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.