Re: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 31/1/07 06:17, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> So in 2.6.16, watchdog thread itself promises max timeout
> to about 1s by hooking a timer, while In 2.6.18, the max timeout
> value is volatile

But the softlockup thread implementation has not changed between 2.6.16 and
2.6.18. The periodic delay is caused by the thread itself calling
msleep_interruptible(1000) which should, as part of its implementation,
queue up a timer. So this erratic behaviour on 2.6.18 is still worrying --
it's certainly concerning that clamping the time we block for makes a
difference. It would seem to imply that we are missing work to do sometimes
when we block (e.g., perhaps they are on a timer wheel that we do not check,
or there is some outstanding rcu work that we do not check for, or something
like that). It feels like maybe something about the way that deferred work
is managed has changed a bit in core Linux and the Xen parts haven't caught
up. :-)

 -- Keir



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