From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: Future of xenbits Linux trees Date: Fri, 05 Jun 2009 14:36:37 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" 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: Christian Tramnitz , "xen-devel@lists.xensource.com" Cc: Isaku Yamahata , Jeremy Fitzhardinge List-Id: xen-devel@lists.xenproject.org On 05/06/2009 14:26, "Christian Tramnitz" wrote: > Simple reason, there are so many fundamental changes in/before 2.6.29 > i.e. ext4 and in terms of video support (KMS, GEM) that anything before > 2.6.29 (such as the 2.6.27 XCI tree) will be a waste of efforts if that > will be the next tree that should have long-term (until pvops merges > upstream, haha) support. We don't need to wait for pv_ops to be merged. We just need it to have near-enough feature parity. Actually now it supports HVM guests I'm tempted to just move over to it. It would probably make sense to keep Jeremy as gatekeeper for that tree, which will take some of his time. Otoh I'm not sure spending 100% of your time banging your head against lkml is much fun. :-) Probably the major thing it's missing for a simple complete changeover is ia64/Xen support. We could continue to point the ia64 build target at linux-2.6.18-xen though. -- Keir