From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
systemtap@sources.redhat.com
Subject: Re: [PATCH 5/5] tracing/ftrace: Introduce the big kernel lock tracer
Date: Fri, 24 Oct 2008 14:38:00 -0000 [thread overview]
Message-ID: <20081024143744.GA20768@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2008-10-24 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48F10B0B.406@gmail.com>
[not found] ` <c62985530810210528t416c82b2lbe8471322e8359c@mail.gmail.com>
2008-10-23 18:16 ` Frank Ch. Eigler
2008-10-24 13:44 ` Frédéric Weisbecker
2008-10-24 14:38 ` Frank Ch. Eigler [this message]
2008-10-24 14:48 ` Steven Rostedt
2008-10-24 15:03 ` Frank Ch. Eigler
2008-10-24 15:27 ` Frédéric Weisbecker
2008-10-24 19:30 ` Frank Ch. Eigler
2008-10-29 5:47 ` Tom Zanussi
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=20081024143744.GA20768@redhat.com \
--to=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).