[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



 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
wringer.

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.

    J

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.