From: David Smith <dsmith@redhat.com>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: "Frank Ch. Eigler" <fche@elastic.org>, systemtap@sources.redhat.com
Subject: Re: precompiled probing scenarios
Date: Thu, 19 Oct 2006 20:41:00 -0000 [thread overview]
Message-ID: <4537E30E.2090503@redhat.com> (raw)
In-Reply-To: <C56DB814FAA30B418C75310AC4BB279DCC3BC0@scsmsx413.amr.corp.intel.com>
Stone, Joshua I wrote:
> On Thursday, October 19, 2006 12:50 PM, David Smith wrote:
>> Frank Ch. Eigler wrote:
>>> 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.
>> [...]
>> The hash is computed using the following data:
>> [...]
>> - pass 2 script output
>> [...]
>> Stuff left to do:
>>
>> - Testing, testing, testing
>> - Correct module handling (which Frank outlined above)
>
> Actually, correct module handling should already be covered if you're
> hashing the pass-2 output. Pass-2 is elaboration, which uses debuginfo
> to locate the actual probe points. Suppose I run a script like this:
>
> probe module("*").function("*interrupt*") { log(probefunc()) }
>
> Pass-2 output will include all of the probe points matching my wildcard:
>
> ...
> module("ahci").function("ahci_interrupt@drivers/scsi/ahci.c:889"),
>
> module("libata").function("ata_interrupt@drivers/scsi/libata-core.c:4198
> "),
> ...
>
> If I then load a new module that also has a "*interrupt*" function, the
> pass-2 output will include the new probe point, and will thus get a
> different hash.
Good point. But, if Frank's suggestion was implemented, you could still
use the same cached module, since wildcard expansion would happen at
runtime.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2006-10-19 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` David Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 18:54 Stone, Joshua I
2006-10-26 1:07 ` Frank Ch. Eigler
2006-10-24 0:29 Stone, Joshua I
2006-10-24 15:16 ` David Smith
2006-10-20 20:51 Stone, Joshua I
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-06 19:08 Frank Ch. Eigler
2006-10-06 20:33 ` David Smith
2006-10-06 20:40 ` Frank Ch. Eigler
2006-10-19 19:49 ` David Smith
2006-10-19 21:53 ` Frank Ch. Eigler
2006-10-20 13:50 ` David Smith
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=4537E30E.2090503@redhat.com \
--to=dsmith@redhat.com \
--cc=fche@elastic.org \
--cc=joshua.i.stone@intel.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).