This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: thoughts
- From: "Jose R. Santos" <jrsantos at austin dot ibm dot com>
- To: Mathieu Desnoyers <compudj at krystal dot dyndns dot org>
- Cc: "Jose R. Santos" <jrsantos at austin dot ibm dot com>, Martin Hunt <hunt at redhat dot com>, "Frank Ch. Eigler" <fche at redhat dot com>, systemtap at sources dot redhat dot com
- Date: Thu, 29 Sep 2005 11:43:42 -0500
- Subject: Re: thoughts
- References: <20050926151101.GA5835@rx8.austin.ibm.com> <20050926174442.GB31126@Krystal>
Mathieu Desnoyers <compudj@krystal.dyndns.org> [050926]:
> We are working on a kernel tracing tool that seems to share a lot with the
> trace tool you are talking about.
>
> We have a kernel tracer (LTTng) and a trace viewer (LTTV) which are based on
> static kernel instrumentation.
>
> One of the main advantages of the LTTng tracing code is that it is fast. It
> seems to be a downside of SystemTAP. We use a code generator that takes an event
> description to generate the tracing code that can be inserted through module
> loading.
>
> I think that you might be interested to have a look at it. Here is the website :
> http://ltt.polymtl.ca
Hi Mathieu,
I've been looking at the LTTV component and it is the same basic
concept I wanted to create as part of our project. It would be nice
not to re-write all this from scratch so I'm looking at how to
integrate LTTV into the SystemTap trace functionality that we are
working on.
Thanks
-JRS