[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AC2AF01.9090202@redhat.com>
Date: Tue, 29 Sep 2009 21:06:09 -0400
From: Masami Hiramatsu <mhiramat@...hat.com>
To: Frederic Weisbecker <fweisbec@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...e.hu>,
lkml <linux-kernel@...r.kernel.org>
CC: Thomas Gleixner <tglx@...utronix.de>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Christoph Hellwig <hch@...radead.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Jim Keniston <jkenisto@...ibm.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
systemtap <systemtap@...rces.redhat.com>,
DLE <dle-develop@...ts.sourceforge.net>
Subject: Re: [RFC PATCH tracing/kprobes 0/5] tracing/kprobes, perf: perf
kprobe support
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).
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. :)
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@...hat.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists