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 11:29:29 +0100 [thread overview]
Message-ID: <4D7F3F89.70102@ts.fujitsu.com> (raw)
In-Reply-To: <C9A4E8CD.14CCE%keir.xen@gmail.com>
On 03/15/11 10:58, Keir Fraser wrote:
> On 15/03/2011 09:21, "Juergen Gross"<juergen.gross@ts.fujitsu.com> wrote:
>
>>> That candidate-is-valid check seems absolutely independent of the
>>> particular scheduler used, and hence could be done in the (sole)
>>> caller, thus not requiring any change to the scheduler interface.
>>>
>>> Which at once would eliminate unnecessary calls into pick_cpu (i.e.
>>> you'd call it a second time only if the previously selected CPU really
>>> is no longer valid to be used for that vCPU).
>>
>> True.
>>
>> The patch seems to become smaller :-)
>
> By the way, why is the cpu_isset(new_cpu, v->domain->vcpupool->cpu_valid)
> check required (after calling pick_cpu, in the cuirrently checked-in code)?
Good question. It shouldn't be required, as pick_cpu should check this and
should return only cpus in the current cpupool. With the latest patches from
Jan this seems to be true. :-)
I think I'll send a separate patch to remove the check.
> You already check that pick_cpu was called holding the correct pair of
> locks, if it has returned a cpu that is not in the pool's cpu_valid mask,
> what would make pick_cpu return anything different on the next invocation
> thus avoiding an endless loop?
Nothing. If pick_cpu is returning a cpu outside of it's cpupool, the loop
could be infinite. Inserting a BUG_ON would be a good idea, but this would
require a bit more logic, as a cpu might be removed from the cpupool during
a running vcpu_migrate (this case is handled by the call of
cpu_disable_scheduler() during removing a cpu from a cpupool).
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 10:29 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
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 [this message]
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=4D7F3F89.70102@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.