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

Re: [Xen-devel] [PATCH] Avoid endless loop for vcpu migration


  • To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Tue, 15 Mar 2011 08:50:20 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 15 Mar 2011 01:51:11 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=iY1BY3SswEX/WTt5e48ggZmP8Vc3YRHtZMLzA3NyeRivGh8t8iWLVz+Hjg0k5/Jawd UVR/VGquFwwYNqFzeYOnE3p1nl+QsKPN/D5w5ZDDPKjW2k2NkoYZCwAQFKGwjfisCjzG dTFaAWl1JNQAZzLA2uuBeg70Ro4CUIbQJ2sUE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acvi7gOPtbpbWOXojEaL9qqYoJ1zyw==
  • Thread-topic: [Xen-devel] [PATCH] Avoid endless loop for vcpu migration

On 15/03/2011 08:46, "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxx> wrote:

>> It's not critical, and not affecting correctness. But with updating
>> idle_bias on the first invocation you're (on the right hardware)
>> basically guaranteeing the second invocation to return a
>> different CPU. That way, your loop will be run minimally three
>> times on such systems. I already find it odd to require two
>> iterations when previously this was a strait code path.
> 
> This was wrong. It was always required to hold the schedule lock of the
> picked cpu as well, otherwise a race with cpu hotplug would be possible.

What would that race be? CPU offlining is done in stop_machine context.

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