[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 02 Feb 2007 01:41:22 +0000
  • Delivery-date: Thu, 01 Feb 2007 17:41:07 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAP4q2wADxf1QAAFVV3AAAMUYXAAACCkwAACFZyAAAV9OMAABEoucACBxTEAATS41lQANfeFwAACGefIAAA3TgAAAlVhm
  • Thread-topic: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug

On 2/2/07 01:29, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Yeah, that's the question. I can post it to lkml for an answer. But at the
> same time, do you think whether this patch is OK to be accepted into
> xen tree or not? Whatever the reason lkml may have to change that
> logic, we have to make it working correctly under xen... ;-)
> 
> BTW, I'm not sure for generic tick-less model, but at least for 2.6.18,
> seems s390 is the only user on CONFIG_NO_IDLE_HZ which
> disables softlockup check instead.

We may have to do the same. If the softlockup mechanism is incompatible with
no-idle-hz then we must either:
 1. Fix softlockup mechanism (or provide fallback implementation for
no-idle-hz).
 2. Disable softlockup mechanism.
 3. Disable no-idle-hz, or keep some fallback rate of ticks (your approach).

My own opinion is we should do (1) or (2).

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.