From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Jun Nakajima <jun.nakajima@intel.com>,
Tim Deegan <tim@xen.org>,
Xen-devel List <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>,
"xiantao.zhang@intel.com" <xiantao.zhang@intel.com>
Subject: Re: VM Feature levelling improvements proposal (draft C)
Date: Tue, 18 Feb 2014 13:57:30 -0500 [thread overview]
Message-ID: <5303AD1A.9010100@oracle.com> (raw)
In-Reply-To: <53039F0E.8010302@citrix.com>
On 02/18/2014 12:57 PM, Andrew Cooper wrote:
> AMD has the CPUID override MSRs 0xc001100{4,5} which cover the basic and
> extended feature leaves. Are there any MSRs to cover
> CPUID.0000_000D[ecx=1].eax which contains the 'XSAVEOPT' bit, or
> CPUID.0000_0007[ecx=1].ebx which is the "structured extended" feature
> map? I cant find any reference to new override MSRs in the manuals (or
> with google), or to having cpuid faulting support like Intel cpus.
Re: XSAVEOPT --- there is a bit for XSAVE (MSRC001_1004[58]). And since
you can't use XSAVEOPT without XSAVE (you use the latter to initialize
the save area) I think using this bit would be sufficient.
-boris
prev parent reply other threads:[~2014-02-18 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 16:22 VM Feature levelling improvements proposal (draft C) Andrew Cooper
2014-02-17 16:46 ` Jan Beulich
2014-02-17 17:38 ` Andrew Cooper
2014-02-18 16:42 ` Boris Ostrovsky
2014-02-18 17:57 ` Andrew Cooper
2014-02-18 18:57 ` Boris Ostrovsky [this message]
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=5303AD1A.9010100@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.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 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).