WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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 12:03:06 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 19 Aug 2010 04:04:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C892CC7F.1E788%keir.fraser@xxxxxxxxxxxxx>
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/jBsGQVEpA2nUTbOXXp8Y20RypQAARzTqAAA4esA=
Thread-topic: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
User-agent: Microsoft-Entourage/12.26.0.100708
On 19/08/2010 11:56, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

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

Ah, looking at the logs I see everything is phy: or file: -- no tap:.
Therefore you should test tip of xen-4.0-testing, as the ring.h changes are
not to blame for any regression in testing.

 -- Keir



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