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

[Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Bruce Edge <bruce.edge@xxxxxxxxx>
  • Date: Wed, 10 Nov 2010 10:17:43 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Wed, 10 Nov 2010 10:56:53 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QE/0CzkHAaZLCxhFdoIU4ukUvhdiXWGzh64txhH7K45ueganXlNmOtXjU7hgS+vVhZ FFOSYlcED4PFmljR/K1FD+C9ViiytM3omfKFFzIH0nCh0f2+1b1dTXXFSaWNnhnyi8m7 RjhbGOMij1zfK+5C9yr667tejRU37w3ZHqNWY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On Mon, Nov 8, 2010 at 11:14 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
On 11/08/2010 10:19 AM, Bruce Edge wrote:
> Is there now or will there be a 2.6.36 stable branch, or is the only
> option for this version the next-2.6.36 branch?

No.  xen/next-2.6.36 doesn't exist any more, and it never really
contained anything useful.  xen/next-2.6.37, however, is closely
tracking upstream and I hope will reach functional parity with the
2.6.32-based branches.

>
> In the past Jeremy has posted details on the state and forward goals
> for the major consolidation branches.
> I haven't seen any such details regarding the .36/.37 branches.
> Does any one know what the plans are?

I'll post something the next week or so when we work out what needs to
happen with .37 to get it up to speed.

>
> We've been hanging off of Konrad's  stable/xen-pcifront-0.8.2 branch
> with good results. I'm wondering what our options are now with the
> recent merge storm.

That has been merged into mainline Linux.

I've tried the mainline 2.6.37-rc1 branch and it's highly unstable as a pvops domU with PCI passthough.
It's not a patch on konrad's stable/xen-pcifront-0.8.2 branch which was looking very good around the 10/21 timeframe, but which has also developed it's own set of instabilities recently.
I haven't reported any of the symptoms as I thought I'd let the dist settle before starting the bug reporting.

Is there some other branch that developers working on PCI device drivers in a pvops domU should be following?

I realize that we're tracking unstable trees, but it's either that or hvm. We'd like to stick with the benefits that pvops provides, but I'm running out of branches to try.

The last stable domU I built was:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git - stable/xen-pcifront-0.8.2
 8029255fcc3a7925ad8ee9f5fdc0764b6662301e
Thu Oct 21 09:36:07 2010 -0400

Do we need to stick with this for a while until the mainline or some other xen/pvops branch stabilizes?

-Bruce
 

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