linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, systemtap@sources.redhat.com
Subject: Re: [PATCH 5/5] tracing/ftrace: Introduce the big kernel lock tracer
Date: Fri, 24 Oct 2008 11:02:39 -0400	[thread overview]
Message-ID: <20081024150239.GB20768@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810241046300.3882@gandalf.stny.rr.com>

Hi -

On Fri, Oct 24, 2008 at 10:47:36AM -0400, Steven Rostedt wrote:
> [...]
> > > 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.
>
> Why can't the userspace application convert the script to something
> easy that the kernel can handle?

That's what we do with the systemtap script, where kernel "handling"
consists of "running the machine code".

> But have the user application interface be very simple, and perhaps
> even use perl or python.

perl and python are pretty big procedural languages, and are not
easily compiled down to compact & quickly executed machine code.  (I
take it no one is suggesting including a perl or python VM in the
kernel.)  Plus, debugger-flavoured event-handling programming style
would not look nearly as compact in perl/python as in systemtap, which
is small and domain-specific.

- FChE

  reply	other threads:[~2008-10-24 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 20:22 [PATCH 5/5] tracing/ftrace: Introduce the big kernel lock tracer Frederic Weisbecker
2008-10-21 12:28 ` Frédéric Weisbecker
2008-10-21 12:33   ` Ingo Molnar
2008-10-21 12:42     ` Frédéric Weisbecker
2008-10-23 18:15   ` Frank Ch. Eigler
2008-10-24 13:43     ` Frédéric Weisbecker
2008-10-24 14:37       ` Frank Ch. Eigler
2008-10-24 14:47         ` Steven Rostedt
2008-10-24 15:02           ` Frank Ch. Eigler [this message]
2008-10-24 15:26             ` Frédéric Weisbecker
2008-10-24 19:29               ` Frank Ch. Eigler
2008-10-29  5:46               ` 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=20081024150239.GB20768@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 NNTP newsgroup(s).