public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	namit@cs.technion.ac.il, hpa@linux.intel.com
Subject: Re: [CFT PATCH v2 0/2] KVM: support XSAVES usage in the host
Date: Tue, 25 Nov 2014 18:13:31 +0800	[thread overview]
Message-ID: <20141125101331.GA28985@kernel> (raw)
In-Reply-To: <1416847414-22253-1-git-send-email-pbonzini@redhat.com>

Hi Paolo,
On Mon, Nov 24, 2014 at 05:43:32PM +0100, Paolo Bonzini wrote:
>The first patch ensures that XSAVES is not exposed in the guest until
>we emulate MSR_IA32_XSS.  The second exports XSAVE data in the correct
>format.
>
>I tested these on a non-XSAVES system so they should not be completely
>broken, but I need some help.  I am not even sure which XSAVE states
>are _not_ enabled, and thus compacted, in Linux.
>
>Note that these patches do not add support for XSAVES in the guest yet,
>since MSR_IA32_XSS is not emulated.
>
>If they fix the bug Nadav reported, I'll add Reported-by and commit.

I test this patchset w/ your "KVM: x86: export get_xsave_addr" patch on 
Skylake and guest hang during boot. The guest screen show "Probing EDD 
(edd=off to disable)... ok", and no more dump.

Regards,
Wanpeng Li 

>
>Thanks,
>
>Paolo
>
>v1->v2: also adjust KVM_SET_XSAVE
>
>Paolo Bonzini (2):
>  kvm: x86: mask out XSAVES
>  KVM: x86: support XSAVES usage in the host
>
> arch/x86/kvm/cpuid.c | 11 ++++++-
> arch/x86/kvm/x86.c   | 87 +++++++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 90 insertions(+), 8 deletions(-)
>
>-- 
>1.8.3.1

  parent reply	other threads:[~2014-11-25 10:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 16:43 [CFT PATCH v2 0/2] KVM: support XSAVES usage in the host Paolo Bonzini
2014-11-24 16:43 ` [CFT PATCH v2 1/2] kvm: x86: mask out XSAVES Paolo Bonzini
2014-11-24 16:43 ` [CFT PATCH v2 2/2] KVM: x86: support XSAVES usage in the host Paolo Bonzini
2014-11-26 12:07   ` Radim Krčmář
2014-11-26 13:13     ` Paolo Bonzini
2014-11-26 13:53       ` Radim Krčmář
2014-11-26 13:57         ` Paolo Bonzini
2014-11-26 14:42           ` Radim Krčmář
2014-11-26 16:26             ` Paolo Bonzini
2014-11-26 17:31               ` Radim Krčmář
2014-12-03 14:23   ` Nadav Amit
2014-12-03 14:26     ` Paolo Bonzini
2014-12-03 18:45       ` Radim Krčmář
2014-12-04 13:43         ` Paolo Bonzini
2014-12-04 13:52           ` Radim Krčmář
2014-11-25 10:13 ` Wanpeng Li [this message]
2014-11-25 10:36   ` [CFT PATCH v2 0/2] KVM: " Paolo Bonzini
2014-11-25 14:05     ` Nadav Amit
2014-11-25 14:17       ` Paolo Bonzini
2014-11-25 14:50         ` Nadav Amit
2014-11-26  1:24           ` Wanpeng Li
2014-11-26  9:00             ` Nadav Amit
2014-11-26  8:47               ` Wanpeng Li
2014-11-26 12:54             ` Paolo Bonzini
2014-12-02  5:16           ` 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=20141125101331.GA28985@kernel \
    --to=wanpeng.li@linux.intel.com \
    --cc=hpa@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namit@cs.technion.ac.il \
    --cc=pbonzini@redhat.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