qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, qemu-devel@nongnu.org,
	dgilbert@redhat.com, amit.shah@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] pc: fix /etc/acpi/tables size in fw_cfg for -M pc-2.0
Date: Thu, 24 Jul 2014 17:22:38 +0200	[thread overview]
Message-ID: <20140724172238.5dcf8f07@nial.usersys.redhat.com> (raw)
In-Reply-To: <1406133466-1824-1-git-send-email-pbonzini@redhat.com>

On Wed, 23 Jul 2014 18:37:44 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:

> Changing the ACPI table size causes migration to break, and the memory
> hotplug work opened our eyes on how horribly we were breaking things in
> 2.0 already.
> 
> Unfortunately when reviewing the design I assumed incorrectly that all
> tables would be placed in separate fw_cfg files.  This would have been
> better, because you can always move stuff to a new SSDT (and thus a new
> file), keeping the sizes under control.
> 
> Hard-code 64k as the maximum ACPI table size; for -M pc-i440fx-2.0
> and -M pc-i440fx-1.7 compute the payload size of QEMU 2.0 and always
> use that one.  This works always for QEMU 2.0, and also for 1.7
> except for a few values of "-smp maxcpus".
> 
> The first patch is needed to shrink the ACPI tables and make them
> smaller than they used to be in 2.0.
> 
> Please test and ack.  I'll do more testing tomorrow.
> 
> Paolo
> 
> 
> Paolo Bonzini (2):
>   acpi-dsdt: procedurally generate _PRT
>   pc: hack for migration compatibility from QEMU 2.0
> 
>  hw/i386/acpi-build.c  | 61 +++++++++++++++++++++++++++++++---
>  hw/i386/acpi-dsdt.dsl | 90 ++++++++++++++++++++++-----------------------------
>  hw/i386/pc_piix.c     | 20 ++++++++++++
>  hw/i386/pc_q35.c      |  5 +++
>  include/hw/i386/pc.h  |  1 +
>  5 files changed, 122 insertions(+), 55 deletions(-)
> 

Aside of my cosmetic comments per-patch,

I've tested series with booting guest in QEMU 1.7, migrating to QEMU 2.1 and rebooting guest there
with WS2003Ex64, WS2008DCx32, WS2012DCx64, WS2012RC2x64 guest OSes,
so on respin you can use my:

Tested-by: Igor Mammedov <imammedo@redhat.com>

      parent reply	other threads:[~2014-07-24 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 16:37 [Qemu-devel] [PATCH 0/2] pc: fix /etc/acpi/tables size in fw_cfg for -M pc-2.0 Paolo Bonzini
2014-07-23 16:37 ` [Qemu-devel] [PATCH 1/2] acpi-dsdt: procedurally generate _PRT Paolo Bonzini
2014-07-23 19:27   ` Laszlo Ersek
2014-07-24  8:22   ` Igor Mammedov
2014-07-23 16:37 ` [Qemu-devel] [PATCH 2/2] pc: hack for migration compatibility from QEMU 2.0 Paolo Bonzini
2014-07-23 19:34   ` Laszlo Ersek
2014-07-24  8:59   ` Igor Mammedov
2014-07-24 14:28     ` Paolo Bonzini
2014-07-24 15:22 ` Igor Mammedov [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=20140724172238.5dcf8f07@nial.usersys.redhat.com \
    --to=imammedo@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).