pre-compiled systemtap modules (try 2)

[David Smith]

Eugeniy Meshcheryakov wrote:
> 13 ??????? 2006 ? 13:12 -0500 David Smith ???????(-??):
>> On Tue, 2006-09-12 at 22:06 -0400, Martin Hunt wrote:
>>> On Tue, 2006-09-12 at 16:39 -0500, David Smith wrote:
>>>
>>>> 1) Command-line interface.  To make this easy for a user to do, we need
>>>> to modify the stap command to save a kernel module and run an existing
>>>> one.  I've attached an updated patch that modifies the systemtap front
>>>> end to take 2 new options:
>>>>
>>>>    -S DIR     Save the compiled module in DIR
>>>>    -P PRE_COMPILED_MODULE
>>>>               Run pre-compiled module
>>> Instead of "-P", why not have stap just realize it's been given a module
>>> and it automatically does the right thing?
>> Hmm.  You do have a point here, because with the patch it is possible to
>> do something like stupid like "stap -P foo.ko bar.stp".
>>
> Can't systemtap just check if there is ELF signature at the begining of
> the file?

Here's an updated version of the patch that does just that.  So, the 
'-P' option has been removed.

Note however that it doesn't try to differentiate between a kernel 
module and a regular elf executable.

-- 
David Smith
dsmith@redhat.com
Red Hat, Inc.
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pre_compiled.patch
Type: text/x-patch
Size: 26261 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20060914/e996cdb4/attachment.bin>