From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Yunhong Jiang <yunhong.jiang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: [PATCH] Allocate vmcs pages when system booting
Date: Fri, 15 Jan 2010 09:30:15 +0000 [thread overview]
Message-ID: <4B5043B8020000780002A2E9@vpn.id2.novell.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD926511497CCC0B7@shzsmsx501.ccr.corp.intel.com>
>>> "Jiang, Yunhong" <yunhong.jiang@intel.com> 15.01.10 10:06 >>>
>b) Can we still turn to the original patch, i.e. pre-allocate all VMCS pages for all possible CPU?
I'm generally opposed to pre-allocations, at least as long as all CPUs are
considered 'possible'. Building with a relatively high nr_cpus= setting
and then running on a relatively small system results in (close to)
unacceptable overhead.
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.
Jan
next prev parent reply other threads:[~2010-01-15 9:30 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 [this message]
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
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=4B5043B8020000780002A2E9@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.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).