From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] isapc: Remove unnecessary migration compatibility code
Date: Tue, 10 Oct 2017 13:42:04 +0200 [thread overview]
Message-ID: <20171010134204.135a9425@nial.brq.redhat.com> (raw)
In-Reply-To: <20171006132502.9191-1-ehabkost@redhat.com>
On Fri, 6 Oct 2017 10:25:02 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> We don't touch isapc when we change guest ABI and add new entries
> to PC_COMPAT_* or new PCMachineClass compat flags. This means
> isapc never guaranteed guest ABI and cross-QEMU-version live
> migration compatibility. There's no point in keeping code for
> kvm-pv-eoi and APIC ID compatibility in pc_init_isa().
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/i386/pc_piix.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
> index 9ff79b1fd9..31646e63c4 100644
> --- a/hw/i386/pc_piix.c
> +++ b/hw/i386/pc_piix.c
> @@ -378,8 +378,6 @@ static void pc_compat_0_13(MachineState *machine)
>
> static void pc_init_isa(MachineState *machine)
> {
> - x86_cpu_change_kvm_default("kvm-pv-eoi", NULL);
> - enable_compat_apic_id_mode();
> pc_init1(machine, TYPE_I440FX_PCI_HOST_BRIDGE, TYPE_I440FX_PCI_DEVICE);
> }
>
next prev parent reply other threads:[~2017-10-10 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 13:25 [Qemu-devel] [PATCH] isapc: Remove unnecessary migration compatibility code Eduardo Habkost
2017-10-10 11:42 ` Igor Mammedov [this message]
2017-10-10 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=20171010134204.135a9425@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@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).