public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: jan.kiszka@siemens.com, anthony@codemonkey.ws,
	kvm@vger.kernel.org, Frank Arnold <frank.arnold@amd.com>
Subject: Re: [PATCH] KVM: Fix XSAVE feature bit enumeration
Date: Sun, 19 Jun 2011 16:29:12 +0300	[thread overview]
Message-ID: <4DFDF9A8.9050108@redhat.com> (raw)
In-Reply-To: <1307714188-6610-1-git-send-email-andre.przywara@amd.com>

On 06/10/2011 04:56 PM, Andre Przywara wrote:
> When iterating through the XSAVE feature enumeration CPUID leaf (0xD)
> we should not stop at the first zero EAX, but instead keep scanning
> since there are gaps in the enumeration (ECX=1 for instance).
> This fixes the proper usage of AVX in KVM guests.

Thanks, applied to uq/master.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-06-19 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 12:08 [PATCH] QEMU: Fix KVM XSAVE feature bit enumeration Andre Przywara
2011-06-10 13:31 ` Jan Kiszka
2011-06-10 13:56   ` [PATCH] KVM: Fix " Andre Przywara
2011-06-19 13:29     ` Avi Kivity [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=4DFDF9A8.9050108@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=anthony@codemonkey.ws \
    --cc=frank.arnold@amd.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.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