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

xen-devel

[Top] [All Lists]

Re: [Xen-devel] RFC: Xen 3.1.1

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: Xen 3.1.1
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Tue, 4 Sep 2007 01:32:18 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: 2007年9月05日 08:34:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C301DA12.15211%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C301DA12.15211%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Sep 03, 2007 at 03:34:42PM +0100, Keir Fraser wrote:
> We're planning to roll an update to the 3.1 branch, hopefully towards the
> end of next week.
That seems awfully quick, given that we can't yet see what will be in the
release?
Top of my list are all the patches that implement missing Xen API stuff
such as 15275:b643179d7452
Also the managed domain foibles like 15149:8fcefab1d63b and
15394:168b143a1a88, etc.
Both of these groups of patches are essentially finishing stuff that
should have been in the release already so seem important.
15161:e046da853ffc - whilst an RFE, this would be very nice to have.
15164:d93e560c1d50
15165:4730ec3d5ab3
15179:152dc0d812b2 - these are essentially about not losing data
15621:f85acff5bef5, 15251:6f06bd06ef47 and related - low risk but
without these ballooning patches, dom0 behaviour can become pathological
15253:ebe4140fe4f8 - this was a nasty little bug
15283:e08cbd487414 - reflect current reality
15671:0c79a9414f8d, 15673:f343d3c16dcc, 15674:07364f8574b8 - nasty
random corruption?
regards
john
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] RFC: Xen 3.1.1 , Keir Fraser
Next by Date: [Xen-devel] [PATCH] Fix error message for xm trigger command , Masaki Kanno
Previous by Thread: RE: [Xen-devel] RFC: Xen 3.1.1 , James Harper
Next by Thread: [Xen-devel] Bind different tasks' evtchns to different vcpus of Dom0 , Cui, Dexuan
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /