This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [Ksummit-2008-discuss] DTrace
- From: Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>
- To: Theodore Tso <tytso at mit dot edu>
- Cc: "Frank Ch. Eigler" <fche at redhat dot com>, ksummit-2008-discuss at lists dot linux-foundation dot org, systemtap at sources dot redhat dot com
- Date: Tue, 1 Jul 2008 10:58:53 +0530
- Subject: Re: [Ksummit-2008-discuss] DTrace
- References: <20080630010423.GA7068@redhat.com> <20080630181959.GA7988@mit.edu>
- Reply-to: ananth at in dot ibm dot com
On Mon, Jun 30, 2008 at 02:19:59PM -0400, Theodore Tso wrote:
> On Sun, Jun 29, 2008 at 09:04:23PM -0400, Frank Ch. Eigler wrote:
> > * tapsets
> >
> > Theodore is mistaken that we are deflecting the job of tapset (probe
> > macro; abstracting architecture and kernel version-change -
> > $foo->bar->baz, function names) authorship. We have asked for help,
> > and have received a little, but the group has in fact authored a
> > growing collection of this stuff.
>
> Well I've heard the line that it's up to the kernel subsystem experts
> to write tapsets from Ulrich Drepper (on the ksummit-2008-discuss
> list) and from Ananth N Mavinakayanahalli (private communication) so I
> think it's fair to say that at least some people associated with
> Systemtap have been placing the blame for the lack of tapsets on the
> kernel developers.
I wouldn't call that 'blame'. What I was trying to say simply was that
kernel subsystem experts are best suited to identify the location and
types of data one could extract from their subsystem. I believe that is
also what Ulrich was trying to say.
Apologies if you felt I was blaming anybody.
Ananth