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.0 RC9 Test Report. Xen: #21087 & Dom0: #4ebd13..

To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Xu, Jiajun" <jiajun.xu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen-4.0.0 RC9 Test Report. Xen: #21087 & Dom0: #4ebd13...
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 07 Apr 2010 08:04:09 +0100
Cc:
Delivery-date: Wed, 07 Apr 2010 00:04:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <789F9655DD1B8F43B48D77C5D30659731D6869B3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcrVZdWHsO3qziLZSsizoRLuswj0mgAB+wXDAADHFWAAK+m8XQ==
Thread-topic: [Xen-devel] Xen-4.0.0 RC9 Test Report. Xen: #21087 & Dom0: #4ebd13...
User-agent: Microsoft-Entourage/12.24.0.100205
On 06/04/2010 11:16, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

> Keir, really thanks for your patch very much. I should not take leave in last
> Friday and this monday :( In fact, although your patch fixed the issue in my
> mail, but there still another bug in PM side for CPU online/offline, which
> will cause panic sometimes, so anyway, CPU online/offline can't pass our
> stress test in xen 4.0.
> I'm testing the patch. Seems it at least passed loop count 500, o*line all
> APs, leaves only BSP online.
> A potential issue in the patch is, in following change, it may trigger the
> assert of __sync_lazy_execstate(), which assume current is idle_vcpu, however,
> at this time, we can't gurrante this. A check for current vcpu is needed.

I looked at the code again, and are you sure about this? As in, have you
seen the assertion trigger? The check that current is the idle_vcpu is only
made 'if(switch_required)', and that can only be the case if we are running
the idle_vcpu! So I think my patch is good as it is, would you agree?

 -- Keir



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