From: Gerd Hoffmann <kraxel@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Victor Kaplansky <victork@redhat.com>,
Marcel Apfelbaum <marcel.a@redhat.com>,
John Snow <jsnow@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [RESEND PATCH] q35: Remove old machine versions
Date: Fri, 18 Dec 2015 10:41:45 +0100 [thread overview]
Message-ID: <1450431705.15674.26.camel@redhat.com> (raw)
In-Reply-To: <1450373244-27585-1-git-send-email-ehabkost@redhat.com>
On Do, 2015-12-17 at 15:27 -0200, Eduardo Habkost wrote:
> Migration with q35 was not possible before commit
> 04329029a8c539eb5f75dcb6d8b016f0c53a031a, because q35 unconditionally
> creates an ich9-ahci device, that was marked as unmigratable. So all q35
> machine classes before pc-q35-2.4 were not migratable, so there's no
> point in keeping compatibility code for them.
>
> Remove all old pc-q35 machine classes and keep only pc-q35-2.4.
> -static void pc_compat_1_6(MachineState *machine)
> -{
> - pc_compat_1_7(machine);
> - rom_file_has_mr = false;
> - has_acpi_build = false;
After applying this patch has_acpi_build is always true and can be
dropped, together with some other code elsewhere which depends on
has_acpi_build. The same is probably true for other variables as well
(gigabyte_align?). Guess it's best to do this as one-per-variable
incremental patches.
Reviewed-by: Gerd Hoffmann <kraxel@gmail.com>
next prev parent reply other threads:[~2015-12-18 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 17:27 [Qemu-devel] [RESEND PATCH] q35: Remove old machine versions Eduardo Habkost
2015-12-17 17:36 ` John Snow
2015-12-17 17:42 ` Eduardo Habkost
2015-12-18 9:41 ` Gerd Hoffmann [this message]
2015-12-18 17:53 ` Eduardo Habkost
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=1450431705.15674.26.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.com \
/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).