mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/3] x86_64,tracing: multiplexing function tracer
Date: Fri, 29 Apr 2011 10:57:10 -0400	[thread overview]
Message-ID: <1304089030.18763.257.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1304088194-6214-1-git-send-email-jolsa@redhat.com>

On Fri, 2011-04-29 at 16:43 +0200, Jiri Olsa wrote:
> hi, me again ;)
> 
> from last RFC email it turned out it'd be good to have support
> for more than 1 currently running function tracers. With
> the possibility to specify separate filter for each of them.

Jiri, I thought I told you to wait, as I'm basically doing the same
thing. Except that I'm gutting the heck out of ftrace.c.

I've been working the last several days rewriting this code.

> 
> I thought about one way how to do that and put it to the
> code for considering. It seems to work properly, though
> I was fighting with set_ftrace_filter for a while.. and
> it is still not ideal ;)

Soon, set_ftrace_filter will only affect the function tracer and not any
other user of function tracing.

I'm almost done. I was hoping to release something today, but it will
probably have to wait till next week.

-- Steve



  parent reply	other threads:[~2011-04-29 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 14:43 Jiri Olsa
2011-04-29 14:43 ` [RFC 1/3] tracing: function tracer registration Jiri Olsa
2011-04-29 14:43 ` [RFC 2/3] tracing: adding statical callers Jiri Olsa
2011-04-29 14:43 ` [RFC 3/3] tracing: set_ftrace_filter support Jiri Olsa
2011-04-29 15:16   ` Steven Rostedt
2011-04-29 14:57 ` Steven Rostedt [this message]
2011-04-29 15:06   ` [RFC 0/3] x86_64,tracing: multiplexing function tracer Jiri Olsa

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=1304089030.18763.257.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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®