mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	fenghua.yu@intel.com, kvm list <kvm@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: KVM causes #GP on XRSTORS
Date: Fri, 21 Nov 2014 03:09:36 +0200	[thread overview]
Message-ID: <AC569D54-4EA9-4090-AE7E-816576BCF2B8@gmail.com> (raw)
In-Reply-To: <20141121001033.GA10834@kernel>


> On Nov 21, 2014, at 02:10, Wanpeng Li <wanpeng.li@linux.intel.com> wrote:
> 
> Hi Nadav,
> On Thu, Nov 20, 2014 at 06:34:04PM +0200, Nadav Amit wrote:
>> Fenghua,
>> 
>> I got KVM (v3.17) crashing on a machine that supports XRSTORS - It appears to get a #GP when it is trying to load the guest FPU.
>> One reason for the #GP is that XCOMP_BV[63] is zeroed on the guest_fpu, but I am not sure it is the only problem.
>> Was KVM ever tested with XRSTORS?
> 
> Current kvm and qemu use standard format and xsaves/xrstors should use
> compact format, in addition, vmx is still not enabled for xsaves/xrstors 
> in kvm.

Sorry, but I don’t quite understand. Should KVM work on a machine that supports xsaves/xrstors?
I am not referring to whether KVM exposes the capability to the guest, but to whether KVM should work at all.

Thanks,
Nadav



  reply	other threads:[~2014-11-21  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AA52FB0B-FB19-4DC0-964B-2984040B15A6@gmail.com>
2014-11-21  0:10 ` Wanpeng Li
2014-11-21  1:09   ` Nadav Amit [this message]
     [not found] ` <546F505F.9080309@redhat.com>
2014-11-24  2:05   ` 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=AC569D54-4EA9-4090-AE7E-816576BCF2B8@gmail.com \
    --to=nadav.amit@gmail.com \
    --cc=fenghua.yu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@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
all inboxes | Powered by JetHome®