From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marcel Apfelbaum <marcel.a@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RESEND v2 0/3] pc: Set hw_version on all machine classes
Date: Tue, 10 Nov 2015 17:44:25 +0200 [thread overview]
Message-ID: <20151110174358-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <564206DF.4030309@redhat.com>
On Tue, Nov 10, 2015 at 04:01:51PM +0100, Paolo Bonzini wrote:
>
>
> On 09/11/2015 21:46, Michael S. Tsirkin wrote:
> > On Mon, Nov 02, 2015 at 12:55:07PM +0100, Paolo Bonzini wrote:
> >> On 30/10/2015 20:36, Eduardo Habkost wrote:
> >>> In 2012, QEMU had a bug where it exposed QEMU version information
> >>> to the guest, meaning a QEMU upgrade would expose different
> >>> hardware to the guest OS even if the same machine-type is being
> >>> used.
> >>>
> >>> The bug was fixed by commit 93bfef4c6e4b23caea9d51e1099d06433d8835a4,
> >>> on all machines up to pc-1.0. But we kept introducing the same
> >>> bug on all newer machines since then. That means we are breaking
> >>> guest ABI every time QEMU was upgraded.
> >>>
> >>> Fix this by setting the hw_version on all PC machines, making
> >>> sure the hardware won't change when upgrading QEMU.
> >>>
> >>> Eduardo Habkost (3):
> >>> pc: Set hw_version on all machine classes
> >>> osdep: Rename qemu_{get,set}_version() to qemu_{,set_}hw_version()
> >>> megasas: Use qemu_hw_version() instead of QEMU_VERSION
> >>>
> >>> hw/arm/nseries.c | 2 +-
> >>> hw/i386/pc_piix.c | 13 +++++++++++++
> >>> hw/i386/pc_q35.c | 10 ++++++++++
> >>> hw/ide/core.c | 2 +-
> >>> hw/scsi/megasas.c | 2 +-
> >>> hw/scsi/scsi-bus.c | 2 +-
> >>> hw/scsi/scsi-disk.c | 2 +-
> >>> include/qemu/osdep.h | 4 ++--
> >>> target-i386/cpu.c | 2 +-
> >>> util/osdep.c | 10 +++++-----
> >>> vl.c | 2 +-
> >>> 11 files changed, 37 insertions(+), 14 deletions(-)
> >>>
> >>
> >> Michael, is it okay for you if I merge this patch series?
> >
> > Sorry about missing this the 1st time around.
> > Let's discuss the right thing to do here -
> > it's a bugfix so we can merge it after hard freeze.
>
> It's already in...
>
> Paolo
How about a patch that just drops QEMU_VERSION from there?
--
MST
prev parent reply other threads:[~2015-11-10 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:36 [Qemu-devel] [PATCH RESEND v2 0/3] pc: Set hw_version on all machine classes Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 1/3] " Eduardo Habkost
2015-11-09 20:45 ` Michael S. Tsirkin
2015-11-10 17:30 ` Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 2/3] osdep: Rename qemu_{get, set}_version() to qemu_{, set_}hw_version() Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 3/3] megasas: Use qemu_hw_version() instead of QEMU_VERSION Eduardo Habkost
2015-11-02 11:55 ` [Qemu-devel] [PATCH RESEND v2 0/3] pc: Set hw_version on all machine classes Paolo Bonzini
2015-11-09 20:46 ` Michael S. Tsirkin
2015-11-10 15:01 ` Paolo Bonzini
2015-11-10 15:44 ` Michael S. Tsirkin [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=20151110174358-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.com \
--cc=pbonzini@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;
as well as URLs for NNTP newsgroup(s).