From: Prasad Sodagudi <psodagud@codeaurora.org>
To: rostedt@goodmis.org, mingo@redhat.com, keescook@chromium.org,
saiprakash.ranjan@codeaurora.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
gregkh@linuxfoundation.org, anton@enomsg.org, arnd@arndb.de,
catalin.marinas@arm.com, ccross@android.com, jbaron@akamai.com,
jim.cromie@gmail.com, joe@perches.com, joel@joelfernandes.org,
psodagud@codeaurora.org
Subject: [PATCH] Register read and writes tracing
Date: Sun, 27 Sep 2020 17:34:49 -0700 [thread overview]
Message-ID: <1601253290-400618-1-git-send-email-psodagud@codeaurora.org> (raw)
Qualcomm team have tried to upstreaming the register trace buffer(RTB) use case earlier - [1]
with pstore approach. In that discussion, there was suggestion to use the ftrace events for
tracking the register reads and writes. In this patch, added register read/write operations
tracing support and also add _no_log variants(for example - readl_relaxed_no_log to readl_relaxed)
functions, which will help to avoid excessive logging for certain register operations
(continuous writes from a loop). These tracepoints can be used by modules
to register probes and log the data convenient for silicon vendor format.
[1] - https://lore.kernel.org/lkml/cover.1535119710.git.saiprakash.ranjan@codeaurora.org/
Qualcomm teams uses these logs for debugging various issues in the product life cycle and
hopping that this logging would help other silicon vendors as this is generic approach.
Please provide your suggestion/comments to bring this patch upstream quality.
Prasad Sodagudi (1):
tracing: Add register read and write tracing support
arch/arm64/include/asm/io.h | 117 ++++++++++++++++++++++++++++++++++++++---
include/linux/iorw.h | 20 +++++++
include/trace/events/rwio.h | 51 ++++++++++++++++++
kernel/trace/Kconfig | 11 ++++
kernel/trace/Makefile | 1 +
kernel/trace/trace_readwrite.c | 30 +++++++++++
6 files changed, 222 insertions(+), 8 deletions(-)
create mode 100644 include/linux/iorw.h
create mode 100644 include/trace/events/rwio.h
create mode 100644 kernel/trace/trace_readwrite.c
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2020-09-28 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 0:34 Prasad Sodagudi [this message]
2020-09-28 0:34 ` [PATCH] tracing: Add register read and write tracing support Prasad Sodagudi
2020-09-28 5:17 ` Greg KH
2020-09-28 5:20 ` Greg KH
2020-09-28 14:55 ` Steven Rostedt
2020-09-28 5:45 ` [PATCH] Register read and writes tracing Sai Prakash Ranjan
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=1601253290-400618-1-git-send-email-psodagud@codeaurora.org \
--to=psodagud@codeaurora.org \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=joe@perches.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=saiprakash.ranjan@codeaurora.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).