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


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

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=sjJNvse5fUhkbcmEr5So4W5PGygJ951U/1YHSUStB48=; b=UIHbgSekzMzvW5vG1cX32+gOKXzssROtOc3P1P8M1LHilgJVDUCTPDbZirlZLp+I1u kfbzRh0Cfd5Ktc5oUmc2zwE1pfhAqFiwNRQEnp6OJbUj3GFXsGX3mGW8h/JryKp2pP0c 9v9pR04WLSpmblwn84w1XnyFT0RcHpSD6egn4=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CD84C1C.3090703@xxxxxxxx>
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: <AANLkTi=AZw8_XJbO=fMD5nfp6Mp9QvWaxRPE8Z7nzq42@xxxxxxxxxxxxxx> <4CD84C1C.3090703@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

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
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?



Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>