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 v3 0/3] kvm: vmx: enable xsaves for kvm
Date: Tue, 02 Dec 2014 14:00:24 +0100 [thread overview]
Message-ID: <547DB7E8.8030601@redhat.com> (raw)
In-Reply-To: <1417518900-42446-1-git-send-email-wanpeng.li@linux.intel.com>
On 02/12/2014 12:14, Wanpeng Li wrote:
> This patchset is to enable xsaves for kvm part, the patch for
> qemu part will be sent out later.
>
> The patchset is tested on skylake-client.
>
> v2 -> v3:
> * add kvm_get/set for ia32_xss
> * fix the type XSS_EXIT_BITMAP
> * load host_xss just once in setup_vmcs_config
> * add/clear atuo switch ia32_xss msr in kvm_get/clear
> * add VMX_XSS_EXIT_BITMAP macro
> * add WARN() in handle_xsaves/xrstors
> * export xsaves if related vmcs field is set
>
> v1 -> v2:
> * auto switch ia32_xss msr just if this msr is present
>
> Wanpeng Li (3):
> kvm: x86: Intel XSAVES vmx and msr handle
> kvm: vmx: add kvm_get/set logic to xsaves
> kvm: x86: Enable Intel XSAVES for guest
>
> arch/x86/include/asm/kvm_host.h | 2 ++
> arch/x86/include/asm/vmx.h | 3 +++
> arch/x86/include/uapi/asm/vmx.h | 6 ++++-
> arch/x86/kvm/cpuid.c | 3 ++-
> arch/x86/kvm/vmx.c | 51 ++++++++++++++++++++++++++++++++++++++++-
> 5 files changed, 62 insertions(+), 3 deletions(-)
>
We need to return false from an svm_xsaves_supported function too, and
we need to prevent setting MSR_IA32_XSS to any non-zero value because
we do not support getting/setting a guest's Trace Packet Configuration
State.
I will squash this hunk in, and send a new patch to return zero for
CPUID(0xd,i).ECX and CPUID(0xd,i).EDX.
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 66d1e3d0195e..6e3a4486749c 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2671,6 +2671,11 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
case MSR_IA32_XSS:
if (!vmx_xsaves_supported())
return 1;
+ /* The only supported bit as of Skylake is bit 8, but
+ * it is not supported on KVM.
+ */
+ if (data != 0)
+ return 1;
vcpu->arch.ia32_xss = data;
if (vcpu->arch.ia32_xss != host_xss)
add_atomic_switch_msr(vmx, MSR_IA32_XSS,
Paolo
next prev parent reply other threads:[~2014-12-02 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 11:14 [PATCH v3 0/3] kvm: vmx: enable xsaves for kvm Wanpeng Li
2014-12-02 11:14 ` [PATCH v3 1/3] kvm: x86: Intel XSAVES vmx and msr handle Wanpeng Li
2014-12-02 11:14 ` [PATCH v3 2/3] kvm: vmx: add kvm_get/set logic to xsaves Wanpeng Li
2014-12-02 13:00 ` Paolo Bonzini [this message]
2014-12-03 0:09 ` [PATCH v3 0/3] kvm: vmx: enable xsaves for kvm 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=547DB7E8.8030601@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