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] New release candidate for Xen 4.0.0 (RC9)

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] New release candidate for Xen 4.0.0 (RC9)
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 26 May 2010 11:02:11 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 May 2010 08:07:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C81993CC.149D7%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>
References: <20100331210716.GA31475@xxxxxxxxxxxxxxxxxxx> <C81993CC.149D7%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, May 19, 2010 at 01:10:36PM +0100, Keir Fraser wrote:
> On 31/03/2010 22:07, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:
> 
> >> I'm only interested in fixing regressions right now for 4.0.0. If this bug
> >> has existed since at least 3.4 then the fix (when we have one!) can wait a
> >> bit longer, for 4.0.1. My guess is that the MTRR interface is getting 
> >> little
> > 
> > Yeah. I get the same failure with 3.4 from xen-3.4-testing:
> 
> I didn't reproduce this with my setup, but the crash below is because
> spin_unlock() is finding that the lock is not locked on entry. This is the
> set_atomicity_lock as acquired/released by prepare_set/post_set. Looking at
> the code they seem to be used in matched pairs and I can't see any memory
> corruption issues or anything. If you want to get this fixed then you'll
> have to add some tracing to find out what's going on (e.g, dump the lock
> state at the end of prepare_set and start of post_set). If you can reproduce
> this deterministically with your setup then should be pretty easy to nail
> this bug.

OK. Thanks.

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

<Prev in Thread] Current Thread [Next in Thread>