From: Martin Hunt <hunt@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: tapset feedback
Date: Thu, 05 Jan 2006 09:28:00 -0000 [thread overview]
Message-ID: <1136453320.4001.11.camel@monkey2> (raw)
In-Reply-To: <20060105090536.BB3E9180B7C@magilla.sf.frob.com>
On Thu, 2006-01-05 at 01:05 -0800, Roland McGrath wrote:
> > One thing I would recommend is a conceptual split between "tapsets",
> > which export probe points and a system library, which would export
> > general-purpose safe functions.
>
> Why is this advantageous? The problems you've cited argue for some kind of
> name spaces or module system for systemtap functions and probes. But I
> don't off hand see how they lead you to conclude that distinguishing these
> two kinds of libraries (function libraries, and probe libraries, which some
> people like to call tapsets).
All I'm proposing is that we have a well-defined and documented set of
library functions. And regardless of how it is implemented, I don't
think we should call it a tapset because it doesn't act like a tapset.
> > A. What if one of the functions matched does not exist in the current
> > kernel? Right now the compilation fails.
>
> What does that mean? A wildcard match will produce some set of actual
> probe points, and all of those will exist in the kernel that matches the
> debuginfo examined.
I'm thinking about tapsets here. For example, "kernel.syscall.*" may
contain functions that the current kernel doesn't implement.
Martin
next prev parent reply other threads:[~2006-01-05 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 8:45 Martin Hunt
2006-01-05 9:05 ` Roland McGrath
2006-01-05 9:28 ` Martin Hunt [this message]
2006-01-05 11:17 ` Roland McGrath
2006-01-05 16:26 ` Martin Hunt
2006-01-05 17:06 ` Frank Ch. Eigler
2006-01-06 9:41 ` Roland McGrath
2006-01-06 9:45 ` Roland McGrath
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=1136453320.4001.11.camel@monkey2 \
--to=hunt@redhat.com \
--cc=roland@redhat.com \
--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).