From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: bsd@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 1/2] target-i386: emulate CPUID level of real hardware
Date: Thu, 18 Jun 2015 17:42:41 +0200 [thread overview]
Message-ID: <5582E6F1.7080001@redhat.com> (raw)
In-Reply-To: <20150618154018.GA10217@potion.brq.redhat.com>
On 18/06/2015 17:40, Radim Krčmář wrote:
> > This unfortunately has to be done only for new machine types. Old types
> > will remain buggy forever.
>
> Ah, ok, which machine type should I target, 2.4?
Yes.
> And is patch 2 is only supposed to work with new machine types?
I'm a bit undecided there, since it only triggers with explicitly
specified CPU flags and the old code would basically never work (it's a
known bug, triggered by libvirt's "host-model" code in some cases).
Paolo
next prev parent reply other threads:[~2015-06-18 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 15:24 [Qemu-devel] [PATCH 0/2] target-i386: fix W10 bug and bring CPUID levels closer to reality Radim Krčmář
2015-06-18 15:24 ` [Qemu-devel] [PATCH 1/2] target-i386: emulate CPUID level of real hardware Radim Krčmář
2015-06-18 15:29 ` Paolo Bonzini
2015-06-18 15:40 ` Radim Krčmář
2015-06-18 15:42 ` Paolo Bonzini [this message]
2015-06-18 17:26 ` Bandan Das
2015-06-18 15:24 ` [Qemu-devel] [PATCH 2/2] target-i386: automatically raise cpuid level to 0xd Radim Krčmář
2015-06-18 15:50 ` Eduardo Habkost
2015-06-18 17:12 ` Bandan Das
2015-06-18 17:26 ` Eduardo Habkost
2015-06-19 9:47 ` Radim Krčmář
2015-06-19 9:54 ` Radim Krčmář
2015-06-19 11:28 ` Radim Krčmář
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=5582E6F1.7080001@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=rth@twiddle.net \
/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).