From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, rkrcmar@redhat.com
Subject: Re: [PATCH 0/9] Final set of XSAVES patches
Date: Fri, 05 Dec 2014 08:27:04 +0100 [thread overview]
Message-ID: <54815E48.3000008@redhat.com> (raw)
In-Reply-To: <20141205011501.GA2683@kernel>
On 05/12/2014 02:15, Wanpeng Li wrote:
> Hi Paolo,
> On Thu, Dec 04, 2014 at 04:57:05PM +0100, Paolo Bonzini wrote:
>> These are all the patches needed to support XSAVES.
>>
>
> I think you miss to add your patch "kvm: x86: mask out XSAVES" to
> this patchset,
That one is already on kvm/next, so it is more or less frozen.
> I test the whole patchset w/ that patch applied on
> skylake-client machine, and it looks good, please feel free to add
> my tested-by to this patchset.
>
> Tested-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Awesome, thanks!
Paolo
>> Paolo Bonzini (5):
>> x86: export get_xsave_addr
>> KVM: x86: support XSAVES usage in the host
>> KVM: x86: use F() macro throughout cpuid.c
>> KVM: cpuid: set CPUID(EAX=0xd,ECX=1).EBX correctly
>> KVM: cpuid: mask more bits in leaf 0xd and subleaves
>>
>> Wanpeng Li (4):
>> kvm: x86: Add kvm_x86_ops hook that enables XSAVES for guest
>> kvm: x86: handle XSAVES vmcs and vmexit
>> kvm: vmx: add MSR logic for XSAVES
>> kvm: vmx: add nested virtualization support for xsaves
>>
>> 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/kernel/xsave.c | 1 +
>> arch/x86/kvm/cpuid.c | 47 ++++++++++++++-------
>> arch/x86/kvm/svm.c | 6 +++
>> arch/x86/kvm/vmx.c | 80 +++++++++++++++++++++++++++++++++++-
>> arch/x86/kvm/x86.c | 90 +++++++++++++++++++++++++++++++++++++----
>> 8 files changed, 210 insertions(+), 25 deletions(-)
>>
>> --
>> 1.8.3.1
prev parent reply other threads:[~2014-12-05 7:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 15:57 [PATCH 0/9] Final set of XSAVES patches Paolo Bonzini
2014-12-04 15:57 ` [PATCH 1/9] x86: export get_xsave_addr Paolo Bonzini
2014-12-04 16:34 ` Greg KH
2014-12-04 17:29 ` Paolo Bonzini
2014-12-04 15:57 ` [PATCH 2/9] KVM: x86: support XSAVES usage in the host Paolo Bonzini
2014-12-04 17:56 ` Radim Krčmář
2014-12-04 15:57 ` [PATCH 3/9] KVM: x86: use F() macro throughout cpuid.c Paolo Bonzini
2014-12-04 15:57 ` [PATCH 4/9] kvm: x86: Add kvm_x86_ops hook that enables XSAVES for guest Paolo Bonzini
2014-12-05 13:32 ` Radim Krčmář
2014-12-04 15:57 ` [PATCH 5/9] KVM: cpuid: set CPUID(EAX=0xd,ECX=1).EBX correctly Paolo Bonzini
2014-12-05 0:40 ` Wanpeng Li
2014-12-04 15:57 ` [PATCH 6/9] KVM: cpuid: mask more bits in leaf 0xd and subleaves Paolo Bonzini
2014-12-05 0:34 ` Wanpeng Li
2014-12-05 1:20 ` Wanpeng Li
2014-12-04 15:57 ` [PATCH 7/9] kvm: x86: handle XSAVES vmcs and vmexit Paolo Bonzini
2014-12-04 18:06 ` Radim Krčmář
2014-12-04 15:57 ` [PATCH 8/9] kvm: vmx: add MSR logic for XSAVES Paolo Bonzini
2014-12-04 18:05 ` Radim Krčmář
2014-12-04 18:07 ` Radim Krčmář
2014-12-04 15:57 ` [PATCH 9/9] kvm: vmx: add nested virtualization support for xsaves Paolo Bonzini
2014-12-04 18:08 ` Radim Krčmář
2014-12-05 1:15 ` [PATCH 0/9] Final set of XSAVES patches Wanpeng Li
2014-12-05 7:27 ` Paolo Bonzini [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=54815E48.3000008@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--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