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: Joel Becker <Joel.Becker@xxxxxxxxxx>
Subject: [Xen-users] Re: Merge Xen (the hypervisor) into Linux
From: david@xxxxxxx
Date: Tue, 2 Jun 2009 19:00:35 -0700 (PDT)
Cc: "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, "jens.axboe@xxxxxxxxxx" <jens.axboe@xxxxxxxxxx>, "npiggin@xxxxxxx" <npiggin@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "kurt.hackel@xxxxxxxxxx" <kurt.hackel@xxxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, Stephen Spector <stephen.spector@xxxxxxxxxx>, "avi@xxxxxxxxxx" <avi@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "wimcoekaerts@xxxxxxxxxxxx" <wimcoekaerts@xxxxxxxxxxxx>, Steven Rostedt <rostedt@xxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, ksrinivasan <ksrinivasan@xxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxxxxx>, "gregkh@xxxxxxx" <gregkh@xxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "EAnderson@xxxxxxxxxx" <EAnderson@xxxxxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, David Miller <davem@xxxxxxxxxxxxx>
Delivery-date: Thu, 04 Jun 2009 01:41:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090603010000.GE31976@xxxxxxxxxxxxxxx>
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: <162f4c90-6431-4a2a-b337-6d7451d7b11e@default> <20090528001350.GD26820@xxxxxxx> <4A1F302E.8030501@xxxxxxxx> <20090528.210559.137121893.davem@xxxxxxxxxxxxx> <4A1FCE8E.2060604@xxxxxxxxxxxxx> <20090602224051.GB32428@xxxxxxxxxxx> <20090602232843.GA6577@xxxxxxx> <20090603010000.GE31976@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 1.10 (DEB 962 2008-03-14)
On Tue, 2 Jun 2009, Joel Becker wrote:

[ Speaking as me, no regard to $EMPLOYER ]

On Wed, Jun 03, 2009 at 01:28:43AM +0200, Ingo Molnar wrote:
A lot of Xen legacies could be dropped: the crazy ring1 hack on
32-bit, the various wide interfaces to make pure-software
virtualization limp along. All major CPUs shipped with hardware
virtualization support in the past 2-3 years, so the availability of
VMX and SVM can be taken for granted for such a project.

        The biggest reason I personally want Xen to be in mainline is
PVM.  Dropping PVM is, to me, pretty much saying "let's merge Xen
without taking the useful parts."


        So I want to see PVM continue for a long time.  I'd like it to
be something I can get with mainline Linux.  I don't care if it is dom0,
dom0 and the hypervisor, whatever.  I just don't want to have to be
patching out-of-tree patches for a pretty basic functionality.
        I don't see 2-3 years as a time frame to assume "everyone has
one."  Otherwise, why does Linux have code for x86_32?  Everyone's had a
64bit system for at least that long.  Sure, that's a straw man.  It goes
both ways.

it's always easier to continue to support stuff that you already have in place than it is to add new things.

if the non PVM stuff could be added to the kernel, how much would that simplify the code needed to support PVM? would that reduce the amount of effort that the Xen people need to spend to something that would mean that they would be able to keep up with fairly recent kernels?

or what about getting the non PVM version in, and then making the seperate argument to add PVM support with a different config option ('xen support for older CPU's, note there is a performance degredation if this option is selected'), distros could support Xen in their main kernel package on new hardware, and users like you could enable the slower version.

David Lang

note: I am not an approver in this process, just an interested observer (who doesn't use Xen)

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

<Prev in Thread] Current Thread [Next in Thread>