LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
tom.zanussi@linux.intel.com
Subject: Re: [PATCH v4] [RFC] trace: Add kprobe on tracepoint
Date: Thu, 12 Aug 2021 20:15:59 +0900 [thread overview]
Message-ID: <20210812201559.31f5e520923d768049c8906d@kernel.org> (raw)
In-Reply-To: <20210812000225.68d72f4a@rorschach.local.home>
On Thu, 12 Aug 2021 00:02:25 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 12 Aug 2021 10:27:35 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > I like to prohibit latter one. It is my feeling, but I think it is
> > natural that the eprobe is only for the static events, and I also think
> > dereferencing a pointer-type field in raw-event is more reliable than
> > dereferencing a digit value passed to the synthetic event.
>
> Although I believe we need to attach eprobes to synthetic events, for
> the reasons I stated in my previous email. I'm perfectly happy to
> forbid them from attaching to kprobe or uprobe events. Because,
> honestly, eprobes do not give you anything that a kprobe nor uprobe can
> give you.
Agreed. It is meaningless to put eprobes on kprobes or uprobes.
Thank you,
>
> -- Steve
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-08-12 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 14:14 Tzvetomir Stoyanov (VMware)
2021-08-11 15:03 ` Masami Hiramatsu
2021-08-11 15:22 ` Steven Rostedt
2021-08-12 1:27 ` Masami Hiramatsu
2021-08-12 3:46 ` Steven Rostedt
2021-08-12 9:44 ` Masami Hiramatsu
2021-08-12 11:14 ` Masami Hiramatsu
2021-08-12 4:02 ` Steven Rostedt
2021-08-12 11:15 ` Masami Hiramatsu [this message]
2021-08-12 11:31 ` Masami Hiramatsu
2021-08-12 13:44 ` Steven Rostedt
2021-08-12 15:06 ` Masami Hiramatsu
2021-08-12 15:44 ` Masami Hiramatsu
2021-08-16 21:40 ` Steven Rostedt
2021-08-17 11:52 ` Masami Hiramatsu
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=20210812201559.31f5e520923d768049c8906d@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.com \
--cc=tz.stoyanov@gmail.com \
--subject='Re: [PATCH v4] [RFC] trace: Add kprobe on tracepoint' \
/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
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).