From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] kvm/x86: enlarge number of possible CPUID leaves
Date: Wed, 08 Dec 2010 14:11:31 +0200 [thread overview]
Message-ID: <4CFF75F3.8090409@redhat.com> (raw)
In-Reply-To: <4CFF6873.8010101@amd.com>
On 12/08/2010 01:13 PM, Andre Przywara wrote:
> Avi, Marcello,
>
> can you please commit this simple fix? (turning 40 to 80?)
> Without it QEMU crashes reliably on our new CPUs (they return 46
> leaves) and causes pain in our testing, because we have to manually
> apply this patch on each tree.
Sorry about that, applied now.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-08 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 11:17 [PATCH] kvm/x86: enlarge number of possible CPUID leaves Andre Przywara
2010-12-01 12:24 ` Avi Kivity
2010-12-01 12:55 ` Andre Przywara
2010-12-08 12:14 ` Avi Kivity
2010-12-08 11:13 ` Andre Przywara
2010-12-08 12:11 ` 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=4CFF75F3.8090409@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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