From: Eduardo Habkost <ehabkost@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, qemu-devel@nongnu.org,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] target-i386: automatically raise cpuid level to 0xd
Date: Thu, 18 Jun 2015 14:26:12 -0300 [thread overview]
Message-ID: <20150618172612.GD3874@thinpad.lan.raisama.net> (raw)
In-Reply-To: <jpgfv5puein.fsf@redhat.com>
On Thu, Jun 18, 2015 at 01:12:32PM -0400, Bandan Das wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
>
> > On Thu, Jun 18, 2015 at 05:24:24PM +0200, Radim Krčmář wrote:
> >> We already bump to level 7 if features there are requested, so do the
> >> same for 0xD.
>
> But doesn't bumping to 7 for feat[ebx] have the potential to break
> ABI too ?
It's not the auto-bumping that breaks ABI, but having older
machine-types now exposing different CPUID data to guests after applying
the patch.
The auto-bump to 7 was introduced at the same time we introduced the
first CPUID[7] features, so you couldn't have any running machines that
would break.
--
Eduardo
next prev parent reply other threads:[~2015-06-18 17:26 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
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 [this message]
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=20150618172612.GD3874@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=bsd@redhat.com \
--cc=pbonzini@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 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.