From: Jiri Olsa <jolsa@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH 1/2] ftrace: Add separate handler for ftrace:function event
Date: Wed, 25 Nov 2015 18:12:43 +0100 [thread overview]
Message-ID: <20151125171243.GA2214@krava.brq.redhat.com> (raw)
In-Reply-To: <20151125120257.17e53cab@gandalf.local.home>
On Wed, Nov 25, 2015 at 12:02:57PM -0500, Steven Rostedt wrote:
> On Wed, 25 Nov 2015 17:50:57 +0100
> Jiri Olsa <jolsa@redhat.com> wrote:
>
> > > This seems redundant. I never understood the control_ops that perf uses
> > > in the function tracing infrastructure. Why can't you just register the
> > > event->ops and have that ops set the filtering? Then the ftrace
> > > infrastructure will only call that event handler for the functions its
> > > filtered on. Then you don't need to do it again. Right now ftrace
> > > already does that with the generic "control_ops" that perf uses, but
> > > now you are doing it again. Seems rather pointless.
> >
> > well thats exactly what we are doing.. but as all ops
> > share single callback we need to find the proper event
> > this callback was triggered for
>
> The ftrace_ops has a "private" field for the user to set. Could you
> make that point back to the event that allocated the ftrace_ops?
> Then the callback function could easily get the event that matches the
> ftrace_ops.
aaah did not see this one ;-) that will do.. nice
>
> >
> > currently we use tracepoint callback (perf_tp_event)
> > where the proper event is found based on the event->filter
> >
> > however this is not the case for ftrace:function because
> > filter will not change the event->filter, but the ops filter
>
> Yeah, I'm trying to figure out the paths here. I would love to remove
> the control_ops as that complicates the function tracing code a bit
> more than I would like it to be.
perf is using the control interface to enable and disable function
tracing any time the process (and its events) is scheduled in/out
sched_in(event) -> ftrace_function_local_enable(&event->ftrace_ops)
sched_out(event) -> ftrace_function_local_disable(&event->ftrace_ops)
>
> I just crashed function tracing by function tracing perf doing function
> tracing :-) I'm currently debugging that (and adding more code to help
> debug things like this).
;-)
jirka
next prev parent reply other threads:[~2015-11-25 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:45 Jiri Olsa
2015-11-25 15:45 ` [PATCH 2/2] ftrace: Check sample types only for sampling events Jiri Olsa
2015-11-25 16:19 ` [PATCH 1/2] ftrace: Add separate handler for ftrace:function event Steven Rostedt
2015-11-25 16:50 ` Jiri Olsa
2015-11-25 17:02 ` Steven Rostedt
2015-11-25 17:12 ` Jiri Olsa [this message]
2015-11-25 17:42 ` Steven Rostedt
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=20151125171243.GA2214@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®