From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23184 invoked by alias); 6 Oct 2006 20:40:11 -0000 Received: (qmail 23173 invoked by uid 22791); 6 Oct 2006 20:40:11 -0000 X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNALL,DK_SIGNED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from elastic.org (HELO elastic.org) (69.20.226.105) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Oct 2006 20:40:06 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=elastic.org; b=IkKKGNAMpggvyPME8IFC31sF5/X1alFp9dICDM2Hzs6tKT1GNTaDOZYu+ZrPLswSy5gHHwfyzl7MCCkL3HZpiD66Q/u1T1M6ysuhpV0FfgDoypX/SmPfTqudBSYWdAXw; Received: from fche by elastic.org with local (auth fche) (Exim 4.60) id 1GVwUE-0004Bg-Bc; Fri, 06 Oct 2006 16:40:02 -0400 Date: Fri, 06 Oct 2006 20:40:00 -0000 From: "Frank Ch. Eigler" To: David Smith Cc: systemtap@sources.redhat.com Subject: Re: precompiled probing scenarios Message-ID: <20061006204001.GB4529@elastic.org> References: <20061006190806.GA30553@elastic.org> <4526BD8F.3060002@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4526BD8F.3060002@redhat.com> User-Agent: Mutt/1.4.2.1i Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00043.txt.bz2 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