From: "Frank Ch. Eigler" <fche@elastic.org>
To: David Smith <dsmith@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: precompiled probing scenarios
Date: Fri, 06 Oct 2006 20:40:00 -0000 [thread overview]
Message-ID: <20061006204001.GB4529@elastic.org> (raw)
In-Reply-To: <4526BD8F.3060002@redhat.com>
Hi -
On Fri, Oct 06, 2006 at 03:33:19PM -0500, David Smith wrote:
> [...]
> Hmm. Are we hashing the input script? If so, how does this work with
> probe wildcards? For example, let's say I probe "kernel.function("*")".
> We compile and cache this module. I then plug in a bunch of
> additional hardware, which causes several extra modules to be loaded. I
> then run stap again with the exact same input script. [...]
kernel.function("*") should match exactly what was there before.
Probes on module("*").FOO would be redefined to mean something like
"all modules that we know at translation time that *might* exist, that
also happen to be *loaded* at run time. This aspect of wildcard
expansion would thus take place at run time rather than translate
time. It just so happens that the same module might probe a greater
or lesser number of modules on an actual system. With that proviso,
a script-source-level hash still seems to work.
> Wow. Supporting different kernel versions on the same arch/cpu is
> currently supported. Doing different arch/cpu types is going to be
> difficult. [...]
Yeah, I figure proper cross-architecture compilation would come later.
> [...] Hmm. Is this new staprun.auth variant a setuid program or
> does the user still need sudo privileges?
It could be setuid.
- FChE
next prev parent reply other threads:[~2006-10-06 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 19:08 Frank Ch. Eigler
2006-10-06 20:33 ` David Smith
2006-10-06 20:40 ` Frank Ch. Eigler [this message]
2006-10-19 19:49 ` David Smith
2006-10-19 21:53 ` Frank Ch. Eigler
2006-10-20 13:50 ` David Smith
2006-10-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` David Smith
2006-10-20 18:44 Stone, Joshua I
2006-10-20 19:26 ` David Smith
2006-10-20 19:32 ` Frank Ch. Eigler
2006-10-20 19:50 ` David Smith
2006-10-20 20:13 ` Frank Ch. Eigler
2006-10-23 20:36 ` David Smith
2006-10-20 20:51 Stone, Joshua I
2006-10-24 0:29 Stone, Joshua I
2006-10-24 15:16 ` David Smith
2006-10-25 18:54 Stone, Joshua I
2006-10-26 1:07 ` Frank Ch. Eigler
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=20061006204001.GB4529@elastic.org \
--to=fche@elastic.org \
--cc=dsmith@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).