From: Tim Bird <tim.bird@am.sony.com>
To: "swb6@aber.ac.uk" <swb6@aber.ac.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Ftrace and Systemtap
Date: Wed, 31 Mar 2010 12:26:45 -0700 [thread overview]
Message-ID: <4BB3A1F5.1050902@am.sony.com> (raw)
In-Reply-To: <40fe3da502608d32ff82523c57a62da1.squirrel@webmail.aber.ac.uk>
On 03/31/2010 10:36 AM, swb6@aber.ac.uk wrote:
> Hi,
> I am currently writing up my
> dissertation based on dynamic tracing and reducing the learning curve to
> understanding the UNIX kernel. I used two dynamic tracing technologies
> (Systemtap and Dtrace) to monitor some virtual machines on a network.
> Whilst going over my initial review of technologies in the area of dynamic
> tracing I realised I had underestimated ftrace, and even dismissed it as
> not being dynamic. However I read hear (http://lwn.net/Articles/343766/)
> that you were as of July last year trying to introduce a patch that would
> allow ftrace the ability to dynamically trace. Also it would be completely
> instrumented from the command line without the need to compile a kernel
> module al la Systemtap.
>
> My question is do you think Systemtap will be replaced by ftrace in the
> future if so I feel I may need to include this fact in my updated
> technology review.
Systemtap addresses a different set of needs than ftrace.
Ftrace has been dynamic for some time, but in a different way
than Systemtap.
I don't see either system going away soon.
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
prev parent reply other threads:[~2010-03-31 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 17:36 Ftrace and Systemtap swb6
2010-03-31 19:26 ` Tim Bird [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=4BB3A1F5.1050902@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swb6@aber.ac.uk \
/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