WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-users] Re: Merge Xen (the hypervisor) into Linux

To: Theodore Tso <tytso@xxxxxxx>, 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
Subject: [Xen-users] Re: Merge Xen (the hypervisor) into Linux
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Wed, 03 Jun 2009 13:41:58 +0200
Cc:
Delivery-date: Thu, 04 Jun 2009 02:07:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090603111541.GC31943@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20090602232843.GA6577@xxxxxxx> <793c2ffe-16d3-4e6c-9cd2-32fa089e46a3@default> <20090603024311.GZ31943@xxxxxxx> <4A26263A.7010809@xxxxxxxxxx> <20090603094753.6eb32099@xxxxxxxxxxxxxxxxxxx> <4A263DD3.3090901@xxxxxxxxxx> <20090603111541.GC31943@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2
On 06/03/09 13:15, Theodore Tso wrote:
On Wed, Jun 03, 2009 at 11:09:39AM +0200, Gerd Hoffmann wrote:
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?

No. Xen is stuck with it forever (or at least for a few releases). Even when adding new & better dom0/xen interfaces in the merge process Xen has to keep the old ones to handle the other dom0 guests (NetBSD, Solaris, old 2.6.18 out-of-tree linux kernel). Pretty much like the linux kernel has to keep old syscalls to not break the ABI for the applications, xen has to maintain old hypercalls[1].

Other way around: Apps can use new system calls only when running one recent kernels, and they have to deal with -ENOSYS. Likewise it might be that the pv_ops-based dom0 kernel can provide some features only when running on a recent hypervisor. That will likely be the case for PAT.

cheers,
  Gerd

[1] and other interfaces like trap'n'emulate certain instructions.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users