From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, ian.jackson@eu.citrix.com,
tim@xen.org, jbeulich@suse.com
Subject: Re: [PATCH for 4.7] doc: document that Domain-0 can't be migrated across cpupools
Date: Mon, 9 May 2016 10:53:30 +0200 [thread overview]
Message-ID: <5730500A.5040306@suse.com> (raw)
In-Reply-To: <7454590a-8b02-8f3d-3a9d-45b26af32ebc@citrix.com>
On 09/05/16 10:36, Andrew Cooper wrote:
> On 09/05/2016 09:29, Juergen Gross wrote:
>> Domain-0 is always member of Pool-0 (or, to be precise: of the cpuppol
>> with cpupool-id 0). Document this in the xl man page.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>
> Out of interest, why?
>
> Is this a limitation of the current implementation, or something which
> couldn't be made to work?
>
> Given that it is all just vcpus and linked lists in the end, I can't see
> why this should necessarily be the case.
Main reason was to keep cpu hotplugging simple. New cpus are always
added to Pool-0 and should be available to dom0 immediately without
having to move them to another cpupool.
It could be changed, of course. But I don't see any advantage in
allowing to move dom0 to another cpupool, while the code would be
more complicated.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-09 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:29 [PATCH for 4.7] doc: document that Domain-0 can't be migrated across cpupools Juergen Gross
2016-05-09 8:36 ` Andrew Cooper
2016-05-09 8:53 ` Juergen Gross [this message]
2016-05-09 11:06 ` Wei Liu
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=5730500A.5040306@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).