Re: [Xen-devel] [PATCH] Avoid triggering the softlockup BUG when offline for too long.

[Keir Fraser <keir@xxxxxxxxxxxxx>]

On 27/11/06 4:47 pm, "Glauber de Oliveira Costa" <glommer@xxxxxxxxx> wrote:

>> * stolen time, as well as blocked time, does not have it's corresponding
>> per processor variable updated all in once, but in multiples of
>> NS_PER_TICK chuncks. If we're out for too long, we could detect stolen
>> being too great multiple times, leading to far more calls to the
>> softlockup watchdog then we want too.
> 
> FYI, I just made a simple test checking for stolen time instead of
> offline, and it's in fact called way too oftenly.

That doesn't make sense. Processed_stolen_time should lag at most 1 jiffy
behind actual stolen time. So you still need to accumulate at least 10*HZ-1
jiffies of stolen time in one go to end up touching the softlockup watchdog.
As far as I can see, anyway. What workload did you run to test using stolen
time?

 -- Keir


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