From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] Avoid endless loop for vcpu migration
Date: Tue, 15 Mar 2011 09:53:02 +0100 [thread overview]
Message-ID: <4D7F28EE.20005@ts.fujitsu.com> (raw)
In-Reply-To: <C9A4D8CC.14CBE%keir.xen@gmail.com>
On 03/15/11 09:50, Keir Fraser wrote:
> On 15/03/2011 08:46, "Juergen Gross"<juergen.gross@ts.fujitsu.com> 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.
Ahh, okay.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2011-03-15 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 14:39 [PATCH] Avoid endless loop for vcpu migration Juergen Gross
2011-03-14 15:03 ` Jan Beulich
2011-03-14 15:06 ` Tim Deegan
2011-03-15 5:50 ` Juergen Gross
2011-03-15 7:57 ` Jan Beulich
2011-03-15 8:46 ` Juergen Gross
2011-03-15 8:50 ` Keir Fraser
2011-03-15 8:53 ` Juergen Gross [this message]
2011-03-15 9:01 ` Jan Beulich
2011-03-15 9:21 ` Juergen Gross
2011-03-15 9:34 ` Jan Beulich
2011-03-15 9:58 ` Keir Fraser
2011-03-15 10:29 ` Juergen Gross
2011-03-14 15:06 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7F28EE.20005@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=JBeulich@novell.com \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.