From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, mst@redhat.com, qemu-stable@nongnu.org,
dgilbert@redhat.com, amit.shah@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [RFC for-2.1 for for-2.0-stable] pc: acpi: generate AML only for PCI0 devices if PCI bridge hotplug is disabled
Date: Thu, 24 Jul 2014 12:35:26 +0200 [thread overview]
Message-ID: <53D0E16E.9000801@redhat.com> (raw)
In-Reply-To: <1406192861-30186-1-git-send-email-imammedo@redhat.com>
Il 24/07/2014 11:07, Igor Mammedov ha scritto:
> Fixes migration regression from QEMU-1.7 to a newer QEMUs.
> SSDT table size in QEMU-1.7 doesn't change regardless of
> a number of PCI bridge devices present at startup.
>
> However in QEMU-2.0 since addition of hotplug on PCI bridges,
> each PCI bridge adds ~1875 bytes to SSDT table, including
> pc-i440fx-1.7 machine type where PCI bridge hotplug disabled
> via compat property.
> It breaks migration from "QEMU-1.7" to "QEMU-2.[01] -M pc-i440fx-1.7"
> since RAMBlock size of ACPI tables on target becomes larger
> then on source and migration fails with:
>
> "Length mismatch: /rom@etc/acpi/tables: 2000 in != 3000"
>
> error.
In principle, this definitely makes sense. With QEMU-2.0 and 2.0.1 out
in the wild (and packaged into Ubuntu), however, it's difficult to
decide whether to include this patch or not.
I feel more like having downstreams include it if they skipped QEMU 2.0
and went straight from 1.7 to 2.1.
Paolo
prev parent reply other threads:[~2014-07-24 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 9:07 [Qemu-devel] [RFC for-2.1 for for-2.0-stable] pc: acpi: generate AML only for PCI0 devices if PCI bridge hotplug is disabled Igor Mammedov
2014-07-24 10:35 ` Paolo Bonzini [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=53D0E16E.9000801@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).