[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 22:54:19 +0800
  • Delivery-date: Tue, 30 Jan 2007 06:54:12 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAP4q2wADxf1QAAFVV3AAAMUYXAAACCkwAACFZyAAAV9OMAABEoucAAAWMnAAANBdIA==
  • Thread-topic: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug

>From: Tian, Kevin
>Sent: 2007年1月30日 22:34
>>I wouldn't expect this to make any significant difference to scheduling
>>accounting, certainly over a multi-second time period.
>>
>>Does the time you hoy-unplug the vcpu for make a difference to how
>>often you
>>see this problem? Did you try repro'ing with a 2.6.16 kernel?
>>
>> -- Keir
>
>I can't tell, since I didn't use same pace in each round by manual
>operation. I tried both immediate plug after unplug, and a longer
>interval than 10s. But the first warning jumped out when I finished
>the test and ready to send out the 'good' news. :-(
>
>I'll repro 2.6.16 kernel tomorrow, because remote box crashed just
>now.
>
>Thanks,
>Kevin

I have to say previous change incomplete, because it only limit 
timeout to 1s for very long timeout case (BITS_PER_LONG-3), 
while exclude the case in the middle. I should keep that 1s limit 
on all branches, in case there're some not very long, but longer 
than 10s timeout is hit. However due to crashed box, I have to 
verify it tomorrow too.

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