From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] kvm: x86: revert mask out xsaves
Date: Tue, 02 Dec 2014 09:55:09 +0100 [thread overview]
Message-ID: <547D7E6D.6090000@redhat.com> (raw)
In-Reply-To: <1417500894-7604-1-git-send-email-wanpeng.li@linux.intel.com>
On 02/12/2014 07:14, Wanpeng Li wrote:
> xsaves will be exported to guest in the next patch, so revert the
> mask out xsaves patch.
>
> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
> ---
> arch/x86/kvm/cpuid.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> index a4f5ac4..7af07571 100644
> --- a/arch/x86/kvm/cpuid.c
> +++ b/arch/x86/kvm/cpuid.c
> @@ -320,10 +320,6 @@ static inline int __do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
> F(ADX) | F(SMAP) | F(AVX512F) | F(AVX512PF) | F(AVX512ER) |
> F(AVX512CD);
>
> - /* cpuid 0xD.1.eax */
> - const u32 kvm_supported_word10_x86_features =
> - F(XSAVEOPT) | F(XSAVEC) | F(XGETBV1);
Every single bit needs to be whitelisted independently of the others, so
a full revert is not possible. We need to be careful about post-Skylake
processors introducing new bits in this cpuid leaf.
Also, you cannot just add F(XSAVES) here; you must only do it if XSAVES
is actually supported. This makes sure that nested virtualization will
_not_ present XSAVES to the guests until specific support is introduced
for XSAVES and XRSTORS exits (including the XSS exit bitmap).
In order to do this, you have to introduce a new member in kvm_x86_ops,
modeling what was done for MPX. The second patch can then implement
this new member.
Thanks,
Paolo
> /* all calls to cpuid_count() should be made on the same cpu */
> get_cpu();
>
> @@ -460,8 +456,6 @@ static inline int __do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
> entry->eax &= supported;
> entry->edx &= supported >> 32;
> entry->flags |= KVM_CPUID_FLAG_SIGNIFCANT_INDEX;
> - if (!supported)
> - break;
>
> for (idx = 1, i = 1; idx < 64; ++idx) {
> u64 mask = ((u64)1 << idx);
> @@ -469,9 +463,7 @@ static inline int __do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
> goto out;
>
> do_cpuid_1_ent(&entry[i], function, idx);
> - if (idx == 1)
> - entry[i].eax &= kvm_supported_word10_x86_features;
> - else if (entry[i].eax == 0 || !(supported & mask))
> + if (entry[i].eax == 0 || !(supported & mask))
> continue;
> entry[i].flags |=
> KVM_CPUID_FLAG_SIGNIFCANT_INDEX;
>
next prev parent reply other threads:[~2014-12-02 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 6:14 [PATCH v2 1/2] kvm: x86: revert mask out xsaves Wanpeng Li
2014-12-02 6:14 ` [PATCH v2 2/2] kvm: vmx: enable intel xsaves for guest Wanpeng Li
2014-12-02 8:51 ` Paolo Bonzini
2014-12-02 8:38 ` Wanpeng Li
2014-12-02 8:55 ` Paolo Bonzini [this message]
2014-12-02 8:41 ` [PATCH v2 1/2] kvm: x86: revert mask out xsaves Wanpeng Li
2014-12-03 0:50 ` Wanpeng Li
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=547D7E6D.6090000@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wanpeng.li@linux.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).