[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080723173438.GA23758@redhat.com>
Date: Wed, 23 Jul 2008 13:34:38 -0400
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Adrian Bunk <bunk@...nel.org>
Cc: Arjan van de Ven <arjan@...radead.org>,
Rik van Riel <riel@...hat.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Masami Hiramatsu <mhiramat@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
systemtap@...rceware.org
Subject: Re: systemtap & backward compatibility, was Re: [RFC] systemtap: begin the process of using proper kernel APIs
Hi -
On Wed, Jul 23, 2008 at 07:54:05PM +0300, Adrian Bunk wrote:
> On Wed, Jul 23, 2008 at 12:41:37PM -0400, Frank Ch. Eigler wrote:
> >...
> > In the interim (before we come up with a way of moving more
> > kernel-coupled systemtap code into kernel.org/git), would y'all
> > consider an arrangement? Those of you who care about systemtap, and
> > are intending to make an incompatible kernel/module interface change,
> > please run the systemtap testsuite before & after. [...]
> The number of incompatible kernel/module interface changes per
> kernel is most likely some medium three digit number. What you have
> in mind is therefore not really feasible.
Do you think so, even if the historical pattern continues that only a
small fraction of those changes actually impact systemtap?
> But we have several levels of kernels that incorporate future stuff,
> from -rc over -next to -mm, and you could implement automated runs
> of the systemtap testsuite against the latest ones.
We do some of that already and should do more.
- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists