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] Re: pvops kernel branches - 2.6.36 options, stable/next/

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Thu, 11 Nov 2010 06:58:46 -0800
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 Nov 2010 07:00:20 -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=nsSozW/SedbXD6wa1ttfdlpLb6rxCNdm3Cp8v4PrQhY=; b=IAsUCXLdyGLE05SbBWaOqP4isAXxSr10sqj2olp2L0CmZwLV00UFnerjFW+iCYTuKo ZPAhuEyQeW60fDXY+XWoKtYS71Z5v0CJZbTblnOxAT9d1kF1+5sDBaeu1TSLTgUukMjw VIj01mhfmy9O2fmn98e15UBQltXdxjNl6BwZU=
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=qiiTAGzRBXEA99BqjVyt1s5614Jkd1eOngxe6/50PxrmAVeN5jRjNpqEiy63J6TW9v xydTMQZSeSKFmxS19cs9X2YFUpwjMExToy3m4/RLxozJOlH3syV//IjsPW1sqW5D3IDD 4KvFukeGdXT3EQLaRvjPj7uT9VvLccP6x45Ew=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101110194302.GA25849@xxxxxxxxxxxx>
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> <AANLkTimYoNQKZtm+eBtWVMCdcHop0g-o=wSBjbrHBkRu@xxxxxxxxxxxxxx> <20101110194302.GA25849@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Nov 10, 2010 at 11:43 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
> 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.

Oooh, share please.

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

Well, I am working on a PCI E820 hole thingie,

If this for the 4GB mem limit on pvops domUs?

but those patches are in the
infancy period. There are some fixes:


but they aren't that .. sophisticated.
> 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

Hmm, so the difference between that and the upstream is the PVonHVM and
the initial domain 0 support (all in Stefano's tree).

I tried disabling the  CONFIG_XEN_PVHVM with no change. (see the "2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request" thread.
Is that sufficient to eliminate the PnonHVM from the equation?

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