From: Adrian Bunk <bunk@kernel.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Rik van Riel <riel@redhat.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
systemtap@sourceware.org
Subject: Re: systemtap & backward compatibility, was Re: [RFC] systemtap: begin the process of using proper kernel APIs
Date: Wed, 23 Jul 2008 16:54:00 -0000 [thread overview]
Message-ID: <20080723165405.GE14846@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <y0m3am0blj2.fsf@ton.toronto.redhat.com>
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. If it regresses,
> send us a note or a patch. If practical, we'll integrate it (and add
> any backward-compatibility hacks if needed) into systemtap.
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.
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.
> - FChE
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-07-23 16:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 18:33 [RFC] systemtap: begin the process of using proper kernel APIs (part1: use kprobe symbol_name/offset instead of address) James Bottomley
2008-07-16 22:42 ` Masami Hiramatsu
2008-07-16 23:03 ` James Bottomley
2008-07-17 0:07 ` Masami Hiramatsu
2008-07-17 1:50 ` James Bottomley
2008-07-17 14:18 ` James Bottomley
2008-07-17 16:59 ` James Bottomley
2008-07-17 21:38 ` Masami Hiramatsu
2008-07-17 22:03 ` James Bottomley
2008-07-21 14:21 ` James Bottomley
[not found] ` <1216313914.5515.25.camel__21144.9282979176$1216314027$gmane$org@localhost.localdomain>
2008-07-17 18:32 ` Frank Ch. Eigler
2008-07-17 20:13 ` James Bottomley
2008-07-17 20:28 ` Frank Ch. Eigler
2008-07-17 21:06 ` James Bottomley
2008-07-17 21:35 ` Frank Ch. Eigler
2008-07-17 22:05 ` Masami Hiramatsu
2008-07-22 18:00 ` Rik van Riel
2008-07-22 18:12 ` Frank Ch. Eigler
2008-07-22 18:31 ` Peter Zijlstra
[not found] ` <1216751477.7257.115.camel__19834.5970632092$1216751567$gmane$org@twins>
2008-07-22 18:50 ` Frank Ch. Eigler
2008-07-23 15:06 ` systemtap & backward compatibility, was Re: [RFC] systemtap: begin the process of using proper kernel APIs Frank Ch. Eigler
2008-07-23 15:29 ` Arjan van de Ven
2008-07-23 15:33 ` Peter Zijlstra
2008-07-23 20:26 ` Masami Hiramatsu
[not found] ` <20080723082856.334f9c17__2909.60763018138$1216827051$gmane$org@infradead.org>
2008-07-23 16:43 ` Frank Ch. Eigler
2008-07-23 16:54 ` Adrian Bunk [this message]
2008-07-23 17:43 ` Frank Ch. Eigler
2008-07-23 18:41 ` Adrian Bunk
2008-07-23 22:14 ` Masami Hiramatsu
2008-07-18 9:11 ` [RFC] systemtap: begin the process of using proper kernel APIs (part1: use kprobe symbol_name/offset instead of address) Andi Kleen
2008-07-18 9:23 ` Peter Zijlstra
2008-07-18 10:31 ` Andi Kleen
2008-07-18 10:44 ` Peter Zijlstra
2008-07-18 10:52 ` Andi Kleen
2008-07-18 13:04 ` Frank Ch. Eigler
2008-07-18 13:09 ` Andi Kleen
2008-07-18 13:10 ` Peter Zijlstra
2008-07-18 13:31 ` Frank Ch. Eigler
2008-07-18 13:36 ` Andi Kleen
2008-07-18 13:21 ` James Bottomley
2008-07-18 13:40 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080723165405.GE14846@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arjan@infradead.org \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=riel@redhat.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).