All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org, Frank Arnold <frank.arnold@amd.com>
Subject: Re: [PATCH] KVM: fix XSAVE bit scanning (now properly)
Date: Mon, 13 Jun 2011 11:56:38 +0300	[thread overview]
Message-ID: <4DF5D0C6.8080805@redhat.com> (raw)
In-Reply-To: <1307698530-2453-1-git-send-email-andre.przywara@amd.com>

On 06/10/2011 12:35 PM, Andre Przywara wrote:
> commit 123108f1c1aafd51d6a5c79cc04d7999dd88a930 tried to fix KVMs
> XSAVE valid feature scanning, but it was wrong. It was not considering
> the sparse nature of this bitfield, instead reading values from
> uninitialized members of the entries array.
> This patch now separates subleaf indicies from KVM's array indicies
> and fills the entry before querying it's value.
> This fixes AVX support in KVM guests.

Applied, thanks.

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


      reply	other threads:[~2011-06-13  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  9:35 [PATCH] KVM: fix XSAVE bit scanning (now properly) Andre Przywara
2011-06-13  8:56 ` 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=4DF5D0C6.8080805@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=frank.arnold@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.