This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
RE: Using systemtap cvs to store kprobe testcases
- From: "Lynch, Rusty" <rusty dot lynch at intel dot com>
- To: "William Cohen" <wcohen at redhat dot com>
- Cc: <systemtap at sources dot redhat dot com>
- Date: Wed, 11 May 2005 09:31:45 -0700
- Subject: RE: Using systemtap cvs to store kprobe testcases
Ok, some time later today I'll add module I have been experimenting with
that will act more like a test harness for running multiple testcases.
I just need to add a little more meat to it first.
--rusty
>-----Original Message-----
>From: systemtap-owner@sources.redhat.com [mailto:systemtap-
>owner@sources.redhat.com] On Behalf Of William Cohen
>Sent: Wednesday, May 11, 2005 9:25 AM
>To: Lynch, Rusty
>Cc: systemtap@sources.redhat.com
>Subject: Re: Using systemtap cvs to store kprobe testcases
>
>Lynch, Rusty wrote:
>> Would it be appropriate for me to add a new top level directory to
share
>> kprobe test cases? The systemtap cvs would be convenient, and even
>> though systemtap is really only a consumer of kprobes, if the kprobes
>> implementation has problems then systemtap will probably stumble
across
>> some of those bugs.
>>
>> --rusty
>
>Yes, we discussed adding a testing directory for the kprobes support.
>Having it in the systemtap repository would make things a bit easier.
>There are some example tests on the email list that shoulds be
>contributed to that, e.g. measuring the overhead of kprobe operations.
>
>-Will