From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
seabios@seabios.org, lersek@redhat.com, anthony@codemonkey.ws,
kevin@koconnor.net
Subject: [Qemu-devel] [PATCH RFC 0/3] qemu/acpi-build: cross migration fixes
Date: Thu, 13 Jun 2013 17:29:43 +0300 [thread overview]
Message-ID: <1371133655-10186-1-git-send-email-mst@redhat.com> (raw)
This patchset, on top of my acpi branch,
fixes the issues with cross-version migration:
- Don't add fw cfg entries when running with -M 1.5 and older
- Future proof against future ACPI table changes:
create a ROM blob so the tables are migrated
(together with BIOS)
With these changes the ACPI generation patchset
will become mergeable.
I say *will* since it's only lightly tested,
I intend to test properly and re-post the full patchset
with acpi table geneation in QEMU ready for merge, next week.
Posting for early flames/review.
Michael S. Tsirkin (3):
loader: support for unmapped ROM blobs
acpi: add tables as ROM so they are migrated
acpi-build: disable acpi generation for compat
hw/core/loader.c | 32 +++++++++++++++++++++++++++++---
hw/i386/acpi-build.c | 19 +++++++++++++++++++
hw/i386/pc_piix.c | 12 ++++++++++--
hw/i386/pc_q35.c | 12 ++++++++++--
hw/lm32/lm32_hwsetup.h | 2 +-
include/hw/i386/pc.h | 1 +
include/hw/loader.h | 4 ++--
7 files changed, 72 insertions(+), 10 deletions(-)
--
MST
next reply other threads:[~2013-06-13 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 14:29 Michael S. Tsirkin [this message]
2013-06-13 14:29 ` [Qemu-devel] [PATCH RFC 1/3] loader: support for unmapped ROM blobs Michael S. Tsirkin
2013-06-13 14:29 ` [Qemu-devel] [PATCH RFC 2/3] acpi: add tables as ROM so they are migrated Michael S. Tsirkin
2013-06-13 14:29 ` [Qemu-devel] [PATCH RFC 3/3] acpi-build: disable acpi generation for compat 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=1371133655-10186-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=kevin@koconnor.net \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).