From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
Yunhong Jiang <yunhong.jiang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: RE: [PATCH] Allocate vmcs pages when system booting
Date: Thu, 18 Mar 2010 10:51:36 +0000 [thread overview]
Message-ID: <C7C7B638.2BCBC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BA212510200007800035AF5@vpn.id2.novell.com>
On 18/3/10 10:45, "Jan Beulich" <JBeulich@novell.com> wrote:
>>> In fact it's really not clear to me why cpu_possible_map must be set to
>>> CPU_MASK_ALL - if Linux has ways to avoid this, Xen should have too.
>>
>> Does Linux manage a good reliable job of cutting down cpu_possible_map? That
>> would save cpu_possible_map in my eyes, if we could do that. Otherwise it is
>> indeed pretty useless now. Either way, I'd like cpu hotplug notifier chains
>> in the 4.1 development window.
>
> Only now got to look into this: Linux simply counts the disabled CPUs
> along with the present ones, plus it allows a command line override to
> the number of CPU slots reserved for hotplug. I just put together
> something similar, partly copying code over from there. Will submit
> post-4.0.
Intel are going to submit patches for cpu hotplug notifiers post-4.0, which
is the best solution. I think we can get rid of all possible_map uses in the
end.
-- Keir
next prev parent reply other threads:[~2010-03-18 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 10:52 [PATCH] Allocate vmcs pages when system booting Jiang, Yunhong
2009-11-12 11:22 ` Keir Fraser
2009-11-12 14:58 ` Jiang, Yunhong
2009-11-12 15:04 ` Keir Fraser
2009-11-12 15:15 ` Jiang, Yunhong
2010-01-15 9:06 ` Jiang, Yunhong
2010-01-15 9:30 ` Jan Beulich
2010-01-15 10:31 ` Keir Fraser
2010-01-17 2:02 ` Jiang, Yunhong
2010-01-17 21:35 ` Keir Fraser
2010-01-18 8:11 ` Keir Fraser
2010-01-18 8:22 ` Jiang, Yunhong
2010-03-18 10:45 ` Jan Beulich
2010-03-18 10:51 ` Keir Fraser [this message]
2010-03-19 2:17 ` Jiang, Yunhong
2010-01-15 10:28 ` 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=C7C7B638.2BCBC%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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 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).