To: linux-kernel@vger.kernel.org
From: Kevin Bowling <kevin.bowling@gmail.com>
Subject: Re: [RFC GIT PULL (late)] Xen updates for v2.6.30
Followup-To: gmane.linux.kernel
Date: Thu, 09 Apr 2009 14:35:33 -0700
Message-ID: <grlpna$3sq$1@ger.gmane.org>
References: <20090409181039.GA605@elte.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7Bit
User-Agent: KNode/0.99.01
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1398
Lines: 30

Ingo Molnar wrote:

> Linus,
> 
> Would you still be willing to pull pending Xen updates? They can be
> pulled from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
>    xen-for-linus
> 
> These are late, delayed past the merge window due to the discussions
> around the DOM0 bits and due to an exceptionally busy merge window.

There are a lot of us that would really like to see Xen dom0 merged 
upstream, and several people were disappointed when it didn't go in the 
2.6.30-rc1 merge window (check that thread).  The biggest concern was "do 
people _want_ Xen merged?" rather than any technical problems with the code.    
I think, without a doubt, yes.  Xen is used by many corporations.  It has 
excellent performance, works across platforms that do not have hardware 
virt, and has a proven track record -- check out companies like Linode.com 
and Slicehost.  It also has the maintainership of Citrix, so it is unlikely 
that the code will stagnate or become a burden to other maintainers.

Since the state of Xen dom0 was not addressed in the 2.6.30-rc1 thread, 
please state your intentions here.

Regards,

Kevin


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/