Re: [Xen-devel] [Patch] continue_hypercall_on_cpu rework using tasklets

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 20/04/2010 06:35, "Wei, Gang" <gang.wei@xxxxxxxxx> wrote:

>>> 21172 was not a good changeset to pick. I suggest trying
>>> xen-unstable tip with just 21181/21180 reverted.
>> 
>> Actually, try xen-unstable staging tip (c/s 21202). I've just
>> reimplemented tasklets, so things are quite different at latest tip.
> 
> Just tried c/s 21202, hung up during the 285th S3 resume on system with only
> legacy HPET broadcast. And it is more easy to hung up on HPET MSI broadcast
> capable system - need only <100 times.
> 
> Nothing wrong in the serial log, and ctrl-a didn't respond. I will try to find
> a debuging system with ITP to figure out the hanging point. Meanwhile, I will
> try cpu online/offline stress test see whether it is a general problem in cpu
> online/offline or just S3 specific.

How reliable is S3 in 4.0, for comparison? Did you get it rock solid?

Also, try c/s 21204 before getting into heavy debugging. It fixes being
able to access VMCS fields from c_h_o_c() context. Worth a try.

 -- Keir




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