This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH 0/2] tracing: Tracing integration - dynamic ftrace for SystemTap
- From: Peter Zijlstra <peterz at infradead dot org>
- To: Atsushi Tsuji <a-tsuji at bk dot jp dot nec dot com>
- Cc: linux-kernel at vger dot kernel dot org, rostedt at goodmis dot org, Ingo Molnar <mingo at elte dot hu>, fweisbec at gmail dot com, "Frank Ch. Eigler" <fche at redhat dot com>, paulus at samba dot org, systemtap at sources dot redhat dot com
- Date: Tue, 15 Sep 2009 12:19:33 +0200
- Subject: Re: [PATCH 0/2] tracing: Tracing integration - dynamic ftrace for SystemTap
- References: <4AAF6724.9080201@bk.jp.nec.com> <1253009731.5506.39.camel@laptop>
On Tue, 2009-09-15 at 12:15 +0200, Peter Zijlstra wrote:
> On Tue, 2009-09-15 at 19:06 +0900, Atsushi Tsuji wrote:
> > The patches doesn't contain the performance counters integration,
> > since it is still in development. I think following implementations are
> > needed:
> > - add new type to perf_id (like PERF_TYPE_FTRACE)
> > - add event ids to struct dyn_ftrace
> > - add interfaces to reference event ids by user (via debugfs?)
> > - add probe function to count ftrace events (call do_perf_swcounter_event)
>
> That's long since been done,..
Or are you talking about the mcount thing? Simply expose the mcount hook
as a regular tracepoint and perf can already use it.