From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"Li, Liang Z" <liang.z.li@intel.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] libxc: Expose the pdpe1gb cpuid flag to guest
Date: Tue, 18 Nov 2014 14:26:49 +0000 [thread overview]
Message-ID: <1416320809.17982.14.camel@citrix.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0ABEC9DC@SHSMSX104.ccr.corp.intel.com>
On Tue, 2014-11-18 at 11:41 +0000, Zhang, Yang Z wrote:
> > Hmm - this is a pitfall waiting to happen.
> >
> > In the case that there is a heterogeneous setup with one 1G capable
> > and one 1G incapable server, Xen cannot forcibly prevent the use of 1G
> > pages on the capable hardware. Any VM which guesses at hardware
> > support by means other than cpuid features is liable to explode on migrate.
>
> But a normal guest shouldn't to guess it, right?
IMHO any guest which does not use the mechanism explicitly provided for
feature detection deserves to break randomly.
It's basically equivalent to a physical system where the BIOS masks this
cpuid bit because of some hardware errata or something, the underlying
feature might appear to be present but will have more or less subtle
issues.
Ian.
next prev parent reply other threads:[~2014-11-18 14:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 5:16 [PATCH] libxc: Expose the pdpe1gb cpuid flag to guest Liang Li
2014-11-17 15:39 ` Ian Jackson
2014-11-17 16:24 ` Jan Beulich
2014-11-17 16:30 ` Tim Deegan
2014-11-17 16:40 ` Andrew Cooper
2014-11-17 17:00 ` Tim Deegan
2014-11-17 17:25 ` Andrew Cooper
2014-11-18 10:14 ` Tim Deegan
2014-11-18 10:43 ` Andrew Cooper
2014-11-18 11:41 ` Zhang, Yang Z
2014-11-18 14:26 ` Ian Campbell [this message]
2014-11-18 15:15 ` Tim Deegan
2014-11-19 1:29 ` Zhang, Yang Z
2014-11-19 9:54 ` Tim Deegan
2014-11-25 1:47 ` Zhang, Yang Z
2014-11-25 8:20 ` Jan Beulich
2014-11-26 0:40 ` Zhang, Yang Z
2014-11-28 0:34 ` Li, Liang Z
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=1416320809.17982.14.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=liang.z.li@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@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 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.