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-4.0-testing test] 2032: regressions - FAIL

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 19 Aug 2010 11:56:47 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 19 Aug 2010 03:57:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19565.3089.130734.142300@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs/jBsGQVEpA2nUTbOXXp8Y20RypQAARzTq
Thread-topic: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
User-agent: Microsoft-Entourage/
On 19/08/2010 11:48, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:

> Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions
> - FAIL"):
>> I think we should try e6b9b2cbca5093e8e38d3e314e2f6415ad951c60. This is
>> the commit before e73f4955a821f850f5b88c32d12a81714523a95f which was
>> fingered as bad by the xen-unstable bisect yesterday.
> Shall I try that with current xen-4.0-testing tip, or with the
> changeset I tried last night (pre the netif header backport) ?
> It's likely to take all day so it would be nice to pick the right
> combination.

Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)?
If you don't use blktap then it's utterly immaterial whether you test tip or
two chnagesets back (skipping the ring.h changes), as blktap is the only
subsystem in the Xen tree to use the ring.h header. Linux kernel has its own
copy of that ring.h file and will be unaffected either way.

 -- Keir

Xen-devel mailing list