[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190419150818.1f8ec963@gandalf.local.home>
Date: Fri, 19 Apr 2019 15:08:18 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Raul Rangel <rrangel@...omium.org>
Cc: linux-trace-devel@...r.kernel.org, linux-mmc@...r.kernel.org,
djkurtz@...omium.org, zwisler@...omium.org,
Ludovic Barre <ludovic.barre@...com>,
Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Faiz Abbas <faiz_abbas@...com>, linux-kernel@...r.kernel.org,
Oleksij Rempel <linux@...pel-privat.de>,
Liming Sun <lsun@...lanox.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Ingo Molnar <mingo@...hat.com>,
Prabu Thangamuthu <Prabu.T@...opsys.com>,
Chunyan Zhang <chunyan.zhang@...soc.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCH v1 0/4] Add tracing for SDHCI register access
On Fri, 19 Apr 2019 12:40:13 -0600
Raul Rangel <rrangel@...omium.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
Powered by blists - more mailing lists