RE: [Xen-devel] Xen-4.0.0 RC9 Test Report. Xen: #21087 & Dom0: #4ebd13...

["Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>]

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
>Sent: Tuesday, April 06, 2010 5:45 PM
>To: Xu, Jiajun; xen-devel@xxxxxxxxxxxxxxxxxxx
>Cc: Jiang, Yunhong
>Subject: Re: [Xen-devel] Xen-4.0.0 RC9 Test Report. Xen: #21087 & Dom0:
>#4ebd13...
>
>On 06/04/2010 09:47, "Xu, Jiajun" <jiajun.xu@xxxxxxxxx> wrote:
>
>> Old Open Bugs (3)
>>
>====================================================================
>========
>> 1. System hang after many times cpu online/offline
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1596
>
>I have a potential fix for this which I hope Yunhong Jiang will comment on
>soon. However it is probably too late for 4.0.0 now anyway, which we expect
>to release tomorrow.

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. 

+       /*
+        * If we are running the idle vcpu, sync last non-idle vcpu's state
+        * before changing cpu_online_map. If we are running non-idle vcpu,
+         * we will synchronously sync the state in context_switch() later.
+        */
+       __sync_lazy_execstate();

Again, really thanks for your help on this.

--jyh

>
>Thanks for all your testing efforts! And, of course, more broadly, Intel
>team's bug fixing.
>
> -- Keir


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