From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Christoph Hellwig <hch@infradead.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [RFC PATCH tracing/kprobes 0/5] tracing/kprobes, perf: perf kprobe support
Date: Wed, 30 Sep 2009 14:58:00 -0000 [thread overview]
Message-ID: <20090930145758.GL3361@ghostprotocols.net> (raw)
In-Reply-To: <20090930120418.GB7618@elte.hu>
Em Wed, Sep 30, 2009 at 02:04:18PM +0200, Ingo Molnar escreveu:
>
> * Masami Hiramatsu <mhiramat@redhat.com> wrote:
>
> > Masami Hiramatsu wrote:
> >>
> >> Hi,
> >>
> >> These patches introduce perf kprobe command and update kprobe-tracer.
> >> perf kprobe command allows you to add new probe points by C line number
> >> and local variable names.
> >
> > Last week, Arnaldo and I talked about this command, and he suggested
> > that the command would be better 'perf probe', because it would be
> > able to cover both of kernel space (by kprobes) and user space (by
> > uprobes).
>
> Agreed.
>
> > Basically, I agree with his idea. But I think we may need to consider
> > more flexible syntax for that purpose before we support uprobes. In
> > this area, SystemTap has done big advance, we can see how many
> > varieties of syntax it has by 'man stapprobes'.
> >
> > And also, it's hard to decide it without real uprobe-tracer (and
> > uprobes too!) implementation on ftrace. So, I think it is better to
> > continue using 'perf kprobe' in this time.
> >
> > But it's worth to add to todo list. :)
>
> I'd still name it 'perf probe', even if initially it supports kprobes.
Agreed.
- Arnaldo
prev parent reply other threads:[~2009-09-30 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 19:12 Masami Hiramatsu
2009-09-25 19:13 ` [RFC PATCH tracing/kprobes 2/5] tracing/kprobes: Avoid field name confliction Masami Hiramatsu
2009-09-28 2:21 ` Li Zefan
2009-09-28 16:48 ` Masami Hiramatsu
2009-09-25 19:13 ` [RFC PATCH tracing/kprobes 1/5] tracing/kprobes: Rename special variables syntax Masami Hiramatsu
2009-09-25 19:13 ` [RFC PATCH tracing/kprobes 3/5] tracing/kprobes: Rename fixed field name Masami Hiramatsu
2009-09-25 19:14 ` [RFC PATCH tracing/kprobes 4/5] perf: Support perf kprobe command for kprobe-event setup helper Masami Hiramatsu
[not found] ` <1253955120.12145.2.camel@frodo>
2009-09-28 16:48 ` Masami Hiramatsu
2009-09-25 19:14 ` [RFC PATCH tracing/kprobes 5/5] perf: kprobe command supports without libdwarf Masami Hiramatsu
2009-09-30 1:02 ` [RFC PATCH tracing/kprobes 0/5] tracing/kprobes, perf: perf kprobe support Masami Hiramatsu
2009-09-30 12:04 ` Ingo Molnar
2009-09-30 14:58 ` Arnaldo Carvalho de Melo [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=20090930145758.GL3361@ghostprotocols.net \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=efault@gmx.de \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).