qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH v2 uq/master 0/2] KVM: issues with XSAVE support
Date: Fri, 13 Sep 2013 15:55:56 +0200	[thread overview]
Message-ID: <1379080558-16499-1-git-send-email-pbonzini@redhat.com> (raw)

This series fixes two migration bugs concerning KVM's XSAVE ioctls.
The second right now is only a theoretical problem, since the only
XSAVE-specific state is AVX and all machines with XSAVE also have AVX.
In the future, this will ensure that machines with MPX or AVX-512
do not expose those XSAVE states when using e.g. "-cpu SandyBridge".

Please review.

Paolo Bonzini (2):
  x86: fix migration from pre-version 12
  x86: cpuid: reconstruct leaf 0Dh data

 target-i386/cpu.c | 69 ++++++++++++++++++++++++++++++++++++++++++-------------
 target-i386/cpu.h |  4 ++++
 2 files changed, 57 insertions(+), 16 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2013-09-13 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 13:55 Paolo Bonzini [this message]
2013-09-13 13:55 ` [Qemu-devel] [PATCH v2 uq/master 1/2] x86: fix migration from pre-version 12 Paolo Bonzini
2013-09-13 13:55 ` [Qemu-devel] [PATCH v2 uq/master 2/2] x86: cpuid: reconstruct leaf 0Dh data Paolo Bonzini
2013-10-02 15:21   ` Gleb Natapov
2013-10-02 15:37     ` Paolo Bonzini
2013-10-02 15:39       ` Gleb Natapov
2013-10-02 15:54     ` [Qemu-devel] [PATCH v3 " Paolo Bonzini
2013-10-02 16:03       ` Gleb Natapov
2013-10-03  9:59       ` Igor Mammedov
2013-10-03 10:01         ` Gleb Natapov
2013-10-03 10:14           ` Igor Mammedov
2013-10-02 12:41 ` [Qemu-devel] [PATCH v2 uq/master 0/2] KVM: issues with XSAVE support Paolo Bonzini

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=1379080558-16499-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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).