All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: One question on xen_cpuid in pv guest
Date: Wed, 29 Jul 2009 09:54:55 -0700	[thread overview]
Message-ID: <4A707EDF.1030104@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CDE9D46C@PDSMSX501.ccr.corp.intel.com>

On 07/28/09 20:19, Jiang, Yunhong wrote:
> I have a question to xen_cpuid() in pv_ops guest. Currently the cpuid will be trapped to xen HV for emulation. So why do we still use cpuid_leaf1_edx_mask/cpuid_leaf1_ecx_mask to do mask in guest side? Havn't that been achieved in hypervisor already?
>   

Not entirely, or consistently.  In general Xen masks features which are
outright forbidden for the guest to use, but leaves things that might
possibly be useful - we still need to mask those out.  It also fails to
mask some newer features which are not usable in guests (like GByte
pages and XSAVE), so we need to mask those anyway.  For domU, the set of
mask flags is under the control of the domain config file; a
misconfiguration could enable flags that the kernel can simply not use.

    J

  reply	other threads:[~2009-07-29 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  3:19 One question on xen_cpuid in pv guest Jiang, Yunhong
2009-07-29 16:54 ` Jeremy Fitzhardinge [this message]
2009-07-30  5:44   ` Jiang, Yunhong
2009-07-30 17:06     ` Jeremy Fitzhardinge

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=4A707EDF.1030104@goop.org \
    --to=jeremy@goop.org \
    --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 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.