From: Marcelo Tosatti <mtosatti@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] [qemu-kvm] fix CPUID vendor override
Date: Tue, 13 Apr 2010 13:26:12 -0300 [thread overview]
Message-ID: <20100413162612.GA24991@amt.cnet> (raw)
In-Reply-To: <1271017830-9252-1-git-send-email-andre.przywara@amd.com>
On Sun, Apr 11, 2010 at 10:30:30PM +0200, Andre Przywara wrote:
> the meaning of vendor_override is actually the opposite of how it
> is currently used :-(
> This fix reverts the workaround 4dad7ff3 and replaces it with the
> correct version.
> Fix it to allow KVM to export the non-native CPUID vendor if
> explicitly requested by the user.
>
> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
> ---
> target-i386/cpuid.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> I already sent appropriate patches for upstream qemu git HEAD and
> qemu stable. This fix is especially for qemu-kvm,
> as it differs from upstream QEMU.
>
> Regards,
> Andre.
Applied for both stable and master, thanks.
prev parent reply other threads:[~2010-04-13 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 20:30 [PATCH] [qemu-kvm] fix CPUID vendor override Andre Przywara
2010-04-13 16:26 ` Marcelo Tosatti [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=20100413162612.GA24991@amt.cnet \
--to=mtosatti@redhat.com \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.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