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] Re: Future of xenbits Linux trees

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Future of xenbits Linux trees
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Fri, 05 Jun 2009 19:13:07 +0200
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dulloor <dulloor@xxxxxxxxx>, Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, Christian Tramnitz <chris.ace@xxxxxxx>, Ian@xxxxxxxxxx
Delivery-date: Fri, 05 Jun 2009 10:16:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4FA716B1526C7C4DB0375C6DADBC4EA3417372D258@xxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <h0b67q$lsg$1@xxxxxxxxxxxxx> <C64EDDF5.7916%keir.fraser@xxxxxxxxxxxxx> <940bcfd20906050705x67b51453h715e4d22c9caea61@xxxxxxxxxxxxxx> <4FA716B1526C7C4DB0375C6DADBC4EA3417372D258@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2
On 06/05/09 16:37, Ian Pratt wrote:
One of the reasons cited for sticking on 2.6.18 was that it would
hopefully encourage folk to use pv_ops if they wanted anything more
modern. I'm not sure that worked out too well...

Making the pv_ops kernel the officially one in xen-unstable should work better I think.

It strikes me it's not a bad plan to have two trees, one based
off the latest stable enterprise distro (in this case SLES11), and
the pvops tree based off the latest kernel.org release.

As you've noticed above having two trees (2.6.18 + pv_ops) didn't work out very well so far. I doubt s/2.6.18/2.6.27/ will change that ...

cheers,
  Gerd

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