From: Steven Rostedt <rostedt@goodmis.org>
To: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
<quic_psodagud@quicinc.com>, Marc Zyngier <maz@kernel.org>,
<gregkh@linuxfoundation.org>, <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<mingo@redhat.com>, <jbaron@akamai.com>, <jim.cromie@gmail.com>
Subject: Re: [PATCHv3 3/3] dynamic_debug: Add a flag for dynamic event tracing
Date: Tue, 9 Nov 2021 12:40:46 -0500 [thread overview]
Message-ID: <20211109124046.2a772bcb@gandalf.local.home> (raw)
In-Reply-To: <264b77dd-5509-60f9-248c-a93135b01aa9@quicinc.com>
On Tue, 9 Nov 2021 23:00:11 +0530
Sai Prakash Ranjan <quic_saipraka@quicinc.com> wrote:
> Ah that's a very good idea, descriptor does contain the module, file name.
> We can probably even pass the module name,file name as string from the
> descriptor itself to event?
> Perhaps we can do that for all trace events and not just this trace
> event? Just like the trace event name displayed
> with trace events, perhaps have file name,module name displayed when
> dynamic debug is enabled? Filtering by
> filename is pretty useful since most of these usecases in debugging will
> be with respect to some driver or subsystems.
If we add this for all events, it would require a lot of changes to all
users of tracepoints, as it would require adding a new parameter to the
callbacks.
We could add a flag in the registering that states that the callback is OK
for it, and it passes that data as well.
Let me look into this for a bit. I may not have something this week, but
we should look into this more before adding little hacks that do this one
at a time like this patch.
-- Steve
next prev parent reply other threads:[~2021-11-09 17:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 12:08 [PATCHv3 0/3] tracing/rwmmio/arm64: Add support to trace register reads/writes Sai Prakash Ranjan
2021-11-09 12:08 ` [PATCHv3 1/3] tracing: Add register read/write tracing support Sai Prakash Ranjan
2021-11-09 13:54 ` Steven Rostedt
2021-11-09 14:12 ` Sai Prakash Ranjan
2021-11-10 22:56 ` kernel test robot
2021-11-09 12:08 ` [PATCHv3 2/3] arm64/io: Add a header for mmio access instrumentation Sai Prakash Ranjan
2021-11-09 12:08 ` [PATCHv3 3/3] dynamic_debug: Add a flag for dynamic event tracing Sai Prakash Ranjan
2021-11-09 15:49 ` Steven Rostedt
2021-11-09 16:22 ` Sai Prakash Ranjan
2021-11-09 16:59 ` Steven Rostedt
2021-11-09 17:30 ` Sai Prakash Ranjan
2021-11-09 17:40 ` Steven Rostedt [this message]
2021-11-09 17:49 ` Sai Prakash Ranjan
2021-11-09 21:42 ` Jason Baron
2021-11-09 21:51 ` Steven Rostedt
2021-11-09 22:13 ` Jason Baron
2021-11-09 22:28 ` Steven Rostedt
2021-11-10 20:03 ` Jason Baron
2021-11-11 13:24 ` Mathieu Desnoyers
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=20211109124046.2a772bcb@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_saipraka@quicinc.com \
--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
all inboxes | Powered by JetHome®