From: Steven Rostedt <rostedt@goodmis.org>
To: Raul Rangel <rrangel@chromium.org>
Cc: linux-trace-devel@vger.kernel.org, linux-mmc@vger.kernel.org,
djkurtz@chromium.org, zwisler@chromium.org,
Ludovic Barre <ludovic.barre@st.com>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Faiz Abbas <faiz_abbas@ti.com>,
linux-kernel@vger.kernel.org,
Oleksij Rempel <linux@rempel-privat.de>,
Liming Sun <lsun@mellanox.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ingo Molnar <mingo@redhat.com>,
Prabu Thangamuthu <Prabu.T@synopsys.com>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v1 0/4] Add tracing for SDHCI register access
Date: Fri, 19 Apr 2019 15:08:18 -0400 [thread overview]
Message-ID: <20190419150818.1f8ec963@gandalf.local.home> (raw)
In-Reply-To: <20190419184013.GA145226@google.com>
On Fri, 19 Apr 2019 12:40:13 -0600
Raul Rangel <rrangel@chromium.org> wrote:
> Steven,
> Since it seems this series won't be accepted upstream, would you still be
> open to accepting patches for trace_print_register? I can work on adding
> support to lib traceevent.
It would require having a user in the kernel code.
If you are going to do something out of tree, simply make a helper
function inside your trace event, and then write a plugin for it if you
want to use it for libtraceevent. It allows for custom plugins.
-- Steve
prev parent reply other threads:[~2019-04-19 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 22:08 [PATCH v1 0/4] Add tracing for SDHCI register access Raul E Rangel
2019-04-11 22:08 ` [PATCH v1 1/4] trace_events: Add trace_print_register to print register fields Raul E Rangel
2019-04-11 22:39 ` Steven Rostedt
2019-04-12 15:30 ` Raul Rangel
2019-04-12 15:42 ` Steven Rostedt
2019-04-11 22:08 ` [PATCH v1 2/4] mmc/sdhci: Rename sdhci.c to sdhci-core.c Raul E Rangel
2019-04-11 22:08 ` [PATCH v1 3/4] mmc/host/sdhci: Add register read and write trace events Raul E Rangel
2019-04-11 22:08 ` [PATCH v1 4/4] mmc/host/sdhci: Make sdhci_read/sdhci_write call trace functions Raul E Rangel
2019-04-12 6:26 ` [PATCH v1 0/4] Add tracing for SDHCI register access Adrian Hunter
2019-04-12 14:50 ` Raul Rangel
2019-04-18 6:24 ` Adrian Hunter
2019-04-19 18:40 ` Raul Rangel
2019-04-19 19:08 ` Steven Rostedt [this message]
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=20190419150818.1f8ec963@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=Prabu.T@synopsys.com \
--cc=adrian.hunter@intel.com \
--cc=chunyan.zhang@unisoc.com \
--cc=djkurtz@chromium.org \
--cc=faiz_abbas@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lsun@mellanox.com \
--cc=ludovic.barre@st.com \
--cc=mingo@redhat.com \
--cc=rrangel@chromium.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yamada.masahiro@socionext.com \
--cc=zwisler@chromium.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).