From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [ANNOUNCE] Feature freeze for Xen 4.0 Date: Wed, 09 Dec 2009 11:44:24 -0800 Message-ID: <4B1FFE18.1080904@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Thiago Camargo Martins Cordeiro List-Id: xen-devel@lists.xenproject.org On 12/09/09 07:12, Keir Fraser wrote: > The two are on separate release schedules. We will build the pv_ops kernel > by default when building Xen 4.0 from source, but there's no greater > significance than that. However, Jeremy's pv_ops tree (which of course > tracks mainline) should work well for most dom0 and domU applications. > However, I'd like to make Xen 4 a pre-req for future pvops dom0 kernels, so we can switch to the new APIC setup method. At some point after Xen 4 is officially released, I'll do the cut-over in xen.git. J