From: Steven Rostedt <rostedt@goodmis.org>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "Bird, Tim" <Timothy.Bird@am.sony.com>,
linux kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/4] ftrace - Add function duration tracer to ftrace
Date: Thu, 10 Dec 2009 21:50:29 -0500 [thread overview]
Message-ID: <1260499829.2146.328.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4B21584B.6010405@am.sony.com>
On Thu, 2009-12-10 at 12:21 -0800, Tim Bird wrote:
> It may be moot, given the ensuing discussion (which I'll respond to
> shortly), but here's a link to an uncorrupted version:
>
> http://elinux.org/images/3/3e/Measuring-function-duration-with-ftrace-october-2009.pdf
I just read your presentation, and I like it :-)
I still feel that we don't want to add another plugin, but as I also
stated, I don't want to stop improving on the current plugins until we
have a better alternative.
Would it be possible in making this an trace option (for now). And then
the function graph tracer would just morph into this duration tracer. No
added plugin, but just an option.
I do see value in this, and I don't want to keep it from making it into
34 just because we plan to some day phase out the plugins. There's too
many times we try to go for broke and end up with nothing at the end.
This is why it took so long for streamline_config to make it in.
Just make any tools that interface with this flexible, (abstract layer)
so that if this does change the tools can cope.
-- Steve
prev parent reply other threads:[~2009-12-11 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:40 Tim Bird
2009-12-10 3:41 ` Steven Rostedt
2009-12-10 20:21 ` Tim Bird
2009-12-11 2:50 ` Steven Rostedt [this message]
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=1260499829.2146.328.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=Timothy.Bird@am.sony.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tim.bird@am.sony.com \
/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®