[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Re: Merge Xen (the hypervisor) into Linux
- To: Gerd Hoffmann <kraxel@xxxxxxxxxx>
- From: Theodore Tso <tytso@xxxxxxx>
- Date: Wed, 3 Jun 2009 07:15:41 -0400
- Bcc: tytso@xxxxxxx
- Cc: jeremy@xxxxxxxx, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, jens.axboe@xxxxxxxxxx, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, npiggin@xxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, kurt.hackel@xxxxxxxxxx, x86@xxxxxxxxxx, Stephen Spector <stephen.spector@xxxxxxxxxx>, avi@xxxxxxxxxx, Ingo Molnar <mingo@xxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, wimcoekaerts@xxxxxxxxxxxx, Steven Rostedt <rostedt@xxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, ksrinivasan <ksrinivasan@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, George Dunlap <george.dunlap@xxxxxxxxxxxxx>, gregkh@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, EAnderson@xxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, David Miller <davem@xxxxxxxxxxxxx>
- Delivery-date: Thu, 04 Jun 2009 02:02:54 -0700
- List-id: Xen user discussion <xen-users.lists.xensource.com>
- Mail-followup-to: Theodore Tso <tytso@xxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Steven Rostedt <rostedt@xxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxxxxx>, David Miller <davem@xxxxxxxxxxxxx>, jeremy@xxxxxxxx, avi@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, torvalds@xxxxxxxxxxxxxxxxxxxx, gregkh@xxxxxxx, kurt.hackel@xxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, ksrinivasan <ksrinivasan@xxxxxxxxxx>, EAnderson@xxxxxxxxxx, wimcoekaerts@xxxxxxxxxxxx, Stephen Spector <stephen.spector@xxxxxxxxxx>, jens.axboe@xxxxxxxxxx, npiggin@xxxxxxx
On Wed, Jun 03, 2009 at 11:09:39AM +0200, Gerd Hoffmann wrote:
> On 06/03/09 10:47, Alan Cox wrote:
>>> Linux is not the only player here. NetBSD can run as dom0 guest.
>>> Solaris can run as dom0 guest too. Thus making the dom0/xen interface
>>> private to linux and xen isn't going to fly.
>>
>> It does not however preclude fixing the dom0 interface.
>
> It wasn't my intention to imply that. The interface can be extended
> when needed. PAT support will probably be such a case. Changing it in
> incompatible ways isn't going to work though.
But that means that if there is some fundamentally broken piece of
dom0 design, that the Linux kernel will be stuck with it ***forever***
and it will contaminate code paths and make the code harder to
maintain ***forever*** if we consent to the Xen merge? Is that really
what you are saying? Be careful how you answer that....
- Ted
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
