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/
Home Products Support Community News


Re: [Xen-devel] xen patches are in 2.6.37

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] xen patches are in 2.6.37
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 29 Oct 2010 09:49:57 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, M A Young <m.a.young@xxxxxxxxxxxx>
Delivery-date: Fri, 29 Oct 2010 09:53:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101029094641.GL2804@xxxxxxxxxxx>
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: <alpine.LFD.2.00.1010290834430.16185@xxxxxxxxxxxxxxx> <20101029094641.GL2804@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4
 On 10/29/2010 02:46 AM, Pasi Kärkkäinen wrote:
> On Fri, Oct 29, 2010 at 08:36:54AM +0100, M A Young wrote:
>> Linus has merged branch 'stable/xen-pcifront-0.8.2' of  
>> git://git./linux/kernel/git/konrad/xen
>>   and branch 'for-linus' of  
>> git://xenbits.xen.org/people/sstabellini/linux-pvhvm at
>> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=18cb657ca1bafe635f368346a1676fb04c512edf
> Congratulations to everyone involved!! Great job.
> So what's the next step for dom0 upstreaming? backend drivers? 

Yes, we need to come up with a set of backends that are upstreamable.

There's also a bunch of auxillary things like ACPI power management, CPU
hotplug, etc which need to be adapted and put through the upstreaming

My thoughts about development from now are:

Main Xen development will migrate to the (newly created) xen/next-2.6.37
branch.  At the moment this is more or less exactly upstream, with a
couple of little fixes added.

xen/next-2.6.32 (= xen/stable-2.6.32.x) will move to a more maintenance
state.  They'll be maintained for as long as kernel.org maintains
2.6.32, but the bar for including patches will be higher (definitely
bugfixes, new features if they're not too intrusive, etc).

Therefore the development model will tend towards developing on current
kernels and backporting where necessary, rather than working on old
kernels and forward-porting.


Xen-devel mailing list