From: Prasad Sodagudi <psodagud@codeaurora.org>
To: rostedt@goodmis.org, mingo@redhat.com, keescook@chromium.org,
catalin.marinas@arm.com, saiprakash.ranjan@codeaurora.org,
will@kernel.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,
ccross@android.com, jbaron@akamai.com, jim.cromie@gmail.com,
joe@perches.com, joel@joelfernandes.org,
Prasad Sodagudi <psodagud@codeaurora.org>
Subject: [PATCH 2] Register read and writes tracing
Date: Thu, 5 Nov 2020 18:56:25 -0800 [thread overview]
Message-ID: <1604631386-178312-1-git-send-email-psodagud@codeaurora.org> (raw)
This patch series adds register read/write event tracing
support. Qualcomm team tried upstreaming the register
trace buffer solution - [1] with pstore and dynamic debug
feature but that patch series didn't merge. I have followed
Steve suggestion from -[2] and used tracepoint_enabled() API.
[1] - https://patchwork.kernel.org/project/linux-arm-msm/cover/cover.1536430404.git.saiprakash.ranjan@codeaurora.org/
[2] - https://lore.kernel.org/lkml/20200928105501.7e29df65@oasis.local.home/
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.
v1 -> v2:
- Removed _no_log variant
- tracepoint_enabled api is used.
- Added depends on ARM64
Prasad Sodagudi (1):
tracing: Add register read and write tracing support
arch/arm64/include/asm/io.h | 9 ++++++++
arch/arm64/kernel/image-vars.h | 8 +++++++
include/linux/iorw.h | 38 +++++++++++++++++++++++++++++++
include/trace/events/rwio.h | 51 ++++++++++++++++++++++++++++++++++++++++++
kernel/trace/Kconfig | 11 +++++++++
kernel/trace/Makefile | 1 +
kernel/trace/trace_readwrite.c | 31 +++++++++++++++++++++++++
7 files changed, 149 insertions(+)
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-11-06 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 2:56 Prasad Sodagudi [this message]
2020-11-06 2:56 ` [PATCH v2] tracing: Add register read and write tracing support Prasad Sodagudi
2020-11-06 6:49 ` Greg KH
2020-11-06 9:09 ` Will Deacon
2020-11-06 3:58 ` [PATCH 2] Register read and writes tracing Florian Fainelli
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=1604631386-178312-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 \
--cc=will@kernel.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