[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090812213707.GD5974@nowhere>
Date: Wed, 12 Aug 2009 23:37:09 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Jiaying Zhang <jiayingz@...gle.com>,
Martin Bligh <mbligh@...gle.com>,
Li Zefan <lizf@...fujitsu.com>, Jason Baron <jbaron@...hat.com>
Subject: Re: [RFD] Kprobes/Kretprobes perf support
On Wed, Aug 12, 2009 at 05:27:16PM -0400, Masami Hiramatsu wrote:
> Peter Zijlstra wrote:
> > On Wed, 2009-08-12 at 21:13 +0200, Frederic Weisbecker wrote:
> >
> >> Ingo, Peter do you have an idea on how we could do that?
> >
> > Wouldn't it be easiest to use ftrace to create dynamic tracepoints in
> > the ftrace way such that they become available in
> > debugfs://tracing/events/kprobes/*/ and then have them interfaced the
> > same way as all other tracepoints?
>
> Yes, almost same. One big difference is that they are sharing
> same event-id(TRACE_KPROBE and TRACE_KRETPROBE).
> But I can make each kprobe events to have different ids, if you need.
>
> Thank you,
Yeah that would be better. That's also what Jason did with the syscall events.
--
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