[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070306211105.GD26348@elte.hu>
Date: Tue, 6 Mar 2007 22:11:05 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: "Nakajima, Jun" <jun.nakajima@...el.com>,
virtualization <virtualization@...ts.osdl.org>,
Roland McGrath <roland@...hat.com>,
Anthony Liguori <anthony@...emonkey.ws>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Jan Beulich <jbeulich@...ell.com>
Subject: Re: Xen & VMI?
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> If you're seriously talking about an ABI, [...]
HELLO, this isnt a hypothetical!! The moment there's a xen_paravirt_ops,
Linux has DE FACTO committed itself to the Xen ABI: whatever
functionality the hypercall_page call table plus the int $0x82 interface
offers.
THE MOMENT any of that goes upstream and ships in a distro it's going to
be there forever! Try to change paravirt_ops or any core bit of Linux so
that this ABI cannot be sanely supported: 'fix it, you broke Xen!'. It
wont matter that paravirt_ops is 'internal' to Linux.
so trying to argue as if there was no ABI imposed on Linux by hiding the
Xen ABI behind paravirt_ops, and whistling into the air as if nothing
happened is misguided at best.
Ingo
-
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