This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH 5/5] tracing/ftrace: Introduce the big kernel lock tracer
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: Frédéric Weisbecker <fweisbec at gmail dot com>
- Cc: Ingo Molnar <mingo at elte dot hu>, linux-kernel at vger dot kernel dot org, Steven Rostedt <rostedt at goodmis dot org>, systemtap at sources dot redhat dot com
- Date: Fri, 24 Oct 2008 10:37:44 -0400
- Subject: Re: [PATCH 5/5] tracing/ftrace: Introduce the big kernel lock tracer
- References: <48F10B0B.406@gmail.com> <c62985530810210528t416c82b2lbe8471322e8359c@mail.gmail.com> <y0mmygv18le.fsf@ton.toronto.redhat.com> <c62985530810240643q467a9060kaf906eb7865f0a7@mail.gmail.com>
Hi -
On Fri, Oct 24, 2008 at 03:43:49PM +0200, Frédéric Weisbecker wrote:
> > [...] For comparison, this is how this sort of analysis may be
> > done with systemtap [...]
> That's a great and powerful tool.
>
> But just one sorrow:
> I just think that's a pity that we have to use/learn a new scripting
> language to use it.
I understand.
> I would rather prefer to use an API that provides functions/objects
> for most common scripting languages.
That is an interesting idea. One possible problem is that the final
complete script "program" needs to be translated to something that can
run quickly and safely inside the kernel. Full python or perl runtime
+ libraries would have been almost certainly unbearable.
- FChE