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

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


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 30 Jan 2007 21:15:06 +0800
  • Delivery-date: Tue, 30 Jan 2007 05:14:48 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAP4q2wADxf1QAAIpCVwAAGCUUAAAKkwA
  • Thread-topic: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug

>From: Tian Kevin
>Sent: 2007年1月30日 21:12
>>>>You are confusing the two parts of the softlockup mechanism. The
>thread
>>is
>>responsible only for periodically touching the watchdog. The warning
>>mechanism is driven off the timer interrupt handler. So it is entirely
>>possible for warnings to appear when the thread does not exist (in fact,
>if
>>the thread does not exist then we *expect* warnings to appear!).
>>
>> -- Keir
>
>I added a debug print inside the warning by:
>       printk(KERN_ERR "BUG: drift by 0x%lx\n",
>                        jiffies - touch_timestamp);
>
>This drift doesn't increment monotonically. Most time it is about 1s
>(an interesting fact!), and seldom dozen of seconds. But anyway, it
>indicates that watchdog thread is still scheduled. :-)
>
>Thanks,
>Kevin
>

Sorry that I mean most time 10s here.

Thanks,
Kevin

_______________________________________________
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®.