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

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 16/04/2010 18:51, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

>> We have a stress S3 test upon the Xen 4.1 unstable. Unfortunately, cset 21181
>> cannot pass the stress. It hangs after 48 times S3 suspend/resume.  Another
>> round test even shows it hangs after 2 times suspend/resume. But it is too
>> early to say cset 21181/21180 is the evil, because even cset 21172 (cset
>> ahead
>> of continue_hypercall_on_cpu improvement patch) cannot pass the S3 test
>> either, although it has bigger success suspend/resume times than cset 21181 .
>> so generally, there must be something wrong with S3 logic since Xen 4.0
>> release. We are still trying to dig it out...
> 
> 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.

 Thanks,
 Keir



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