From: David Smith <dsmith@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: systemtap@sources.redhat.com
Subject: Re: precompiled probing scenarios
Date: Fri, 20 Oct 2006 19:50:00 -0000 [thread overview]
Message-ID: <4539288E.7040104@redhat.com> (raw)
In-Reply-To: <20061020193244.GC17981@elastic.org>
Frank Ch. Eigler wrote:
> Hi -
>
> On Fri, Oct 20, 2006 at 02:26:32PM -0500, David Smith wrote:
>> [...]
>> Pass 4: compiled C into "stap_d833fd040735ddde57a23bebb4456542_201.ko"
>
> Is that "_201" at the end the getuid()? I wonder if maybe that could
> be hashed into the content instead.
Nope, that is part of the hash. It might be the number of input bits,
I'm unsure.
I don't hash the getuid(), since:
- by default your cache is stored in your home directory
- who you are doesn't change the pass 2-4 output
>> Copying /tmp/stapYrsXWC/stap_d833fd040735ddde57a23bebb4456542_201.ko to
>> /home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.ko
>> Copying /tmp/stapYrsXWC/stap_d833fd040735ddde57a23bebb4456542_201.c to
>> /home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.c
>
> These messages should probably show up only under -vv (verbosity 2)
> or higher.
Easy enough to fix. Currently they only show up under '-v'.
>> [...]
>> # stap -v -e 'probe begin { log("hi") }' [...]
>> Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 global(s) in
>> 10usr/0sys/11real ms.
>> Using cached result
>> "/home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.ko"
>> as "/tmp/stapJFisJO/stap_d833fd040735ddde57a23bebb4456542_201.ko"
>
> This "Using cached result" part could be rephrased as a pair:
>
> Pass 3: skipped translation
> Pass 4: reused cached module stap_deadbeef
>
>> [...] A module (currently) gets pulled from the cache after pass 2,
>> even if '-p3' or '-p4' was specified on the command line.
>
> The translator would still need to spit out (regenerate) the C source
> code for a -p3 run.
Nope. I actually cache the module and the C file so I can skip pass 3
but still preserve semantics.
Hmm. How about something like:
Pass 3: Using cached
/home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.c
Pass 4: Using cached
/home/dsmith/.stap_cache/d/8/stap_d833fd040735ddde57a23bebb4456542_201.ko
--
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-20 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-10-20 20:13 ` Frank Ch. Eigler
2006-10-23 20:36 ` David Smith
-- 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-19 20:33 Stone, Joshua I
2006-10-19 20:41 ` 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=4539288E.7040104@redhat.com \
--to=dsmith@redhat.com \
--cc=fche@elastic.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).