From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] pc: bring ACPI table size below to 2.0 levels, try fixing -initrd for good
Date: Thu, 02 Oct 2014 15:30:57 +0200 [thread overview]
Message-ID: <542D5391.8080007@redhat.com> (raw)
In-Reply-To: <20141002121140.GA25373@redhat.com>
Il 02/10/2014 14:11, Michael S. Tsirkin ha scritto:
> Summarizing what you say, there are two issues around ACPI tables:
> - linuxboot uses FW CFG to for memory allocations,
> seabios ignores that, so they might conflict.
> Let's fix either linuxboot or seabios (or both!)
> and forget about it.
We can fix linuxboot, it is easy.
These patches do fix John's scenario, but that is not the main issue.
They are not an _attempt_ to fix it, they just do so more or less by
chance. Their real purpose is fixing the second issue:
> - table size changes cause cross version migration issues
> this is really due to the fact we are using RAM
> to migrate ACPI tables.
> IMHO a more robust fix would be to allow RAM size to change
> during migration, or to avoid using RAM, switch to another type of
> object.
Allowing fw_cfg size to change during migration (does not matter if it
is stored in RAM or otherwise) is a huge can of worms because the host
might have loaded the size and stored it somewhere, way before migration.
Extreme example: the guest could expect the size to remain the same at
boot time and S3 resume time.
So I think the fw_cfg size is guest ABI and cannot change across
migration anyway.
> So both issues have other solutions, and I think it's a good
> idea to focus on them for now.
> Also, I really would like to avoid having ACPI sizing-related
> issues for this release. The memory of 2.1.X pain is too fresh :)
Yeah, I understand that. But I think the scary part of this series is
actually the first two patches, rather than the ACPI sizing algorithm.
Paolo
> I'm not NACKing this patchset, but let's
> make some progress on the bigger issues listed above, then come
> back and address sizing as appropriate.
>
> Thanks!
>
>>
>> Paolo Bonzini (6):
>> pc: initialize fw_cfg earlier
>> pc: load the kernel after ACPI tables are built
>> pc: redo sizing of reserved high memory area for -kernel/-initrd
>> pc: introduce new ACPI table sizing algorithm
>> pc: go back to smaller ACPI tables
>> pc: clean up pre-2.1 compatibility code
>>
>> hw/i386/acpi-build.c | 23 +++++++++-------
>> hw/i386/pc.c | 72 +++++++++++++++++----------------------------------
>> hw/i386/pc_piix.c | 32 ++++++++++++++--------
>> hw/i386/pc_q35.c | 7 ++--
>> include/hw/i386/pc.h | 4 ++
>> 5 files changed, 66 insertions(+), 72 deletions(-)
next prev parent reply other threads:[~2014-10-02 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 16:17 [Qemu-devel] [PATCH 0/6] pc: bring ACPI table size below to 2.0 levels, try fixing -initrd for good Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 1/6] pc: initialize fw_cfg earlier Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 2/6] pc: load the kernel after ACPI tables are built Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 3/6] pc: redo sizing of reserved high memory area for -kernel/-initrd Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 4/6] pc: introduce new ACPI table sizing algorithm Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 5/6] pc: go back to smaller ACPI tables Paolo Bonzini
2014-09-18 16:17 ` [Qemu-devel] [PATCH 6/6] pc: clean up pre-2.1 compatibility code Paolo Bonzini
2014-09-19 7:36 ` [Qemu-devel] [PATCH 0/6] pc: bring ACPI table size below to 2.0 levels, try fixing -initrd for good Gerd Hoffmann
2014-09-19 8:06 ` Paolo Bonzini
2014-09-19 13:09 ` Paolo Bonzini
2014-10-02 12:11 ` Michael S. Tsirkin
2014-10-02 12:44 ` Paolo Bonzini
2014-10-02 13:30 ` Paolo Bonzini [this message]
2014-10-02 13:41 ` Michael S. Tsirkin
2014-10-02 13:43 ` Paolo Bonzini
2014-10-02 13:49 ` Michael S. Tsirkin
2014-10-06 13:42 ` Paolo Bonzini
2014-10-06 13:52 ` Michael S. Tsirkin
2014-10-06 13:55 ` Paolo Bonzini
2014-10-06 14:12 ` Michael S. Tsirkin
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=542D5391.8080007@redhat.com \
--to=pbonzini@redhat.com \
--cc=jsnow@redhat.com \
--cc=mst@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 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.