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

Re: [Xen-devel] Tagging Xen 4.0.0 first release candidate

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-devel] Tagging Xen 4.0.0 first release candidate
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 05 Jan 2010 16:06:50 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Tue, 05 Jan 2010 08:07:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7162ab21001050800n7799e2bh998f37d62c29d45@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqOIERWsIzGK+qTTq+ncD9UaedDtAAANJmy
Thread-topic: [Xen-devel] Tagging Xen 4.0.0 first release candidate
User-agent: Microsoft-Entourage/12.23.0.091001
On 05/01/2010 16:00, "Alex Williamson" <alex.williamson@xxxxxx> wrote:

>> It's a bit late for 4.0.0 really. The lack of interest is probably the lack
>> of people hitting the 43-bit limitation built into the current interface.
>> Just about noone is anywhere near close to it.
> 
> Perhaps due to the lack of x86 processors supporting more than 40-bits
> of physical address space that are currently on the market.  But we
> know that's going to change fairly shortly and x86 will finally get
> support for more than 1TB.  That opens the doors for hardware vendors
> to create interesting configurations and maybe not worry so much about
> compressing the address space into a contiguous block.  If Xen can't
> support at least a 44-bit physical address space within the 4.x
> lifetime, it could become a serious limiting factor.  It seems rather
> shortsighted not to prepare for it now, especially given the
> opportunity we have at a major version break.  Thanks,

If it's considered important we can hold up until next week.

 -- Keir



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