From: Gal Hammer <ghammer@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gal Hammer <ghammer@redhat.com>, pbonzini@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH V8 0/3] Virtual Machine Generation ID
Date: Sun, 16 Nov 2014 12:15:56 +0200 [thread overview]
Message-ID: <1416132959-25905-1-git-send-email-ghammer@redhat.com> (raw)
Hi,
The patch grow to three parts now. Although it is still add a QEmu
support for Microsoft's Virtual Machine Generation ID device.
The first is a short device's description, then the ACPI tables
changes and the actual device and the last patch updates the tests'
ACPI tables.
Your comment are welcomed.
Thanks,
Gal.
V8 - Add a device's description file.
- GUID is stored in fw cfg file and the guest writes the
physical address to the device (reduces vmexits).
V7 - Move the device's description back to the static SSDT table.
- The GUID is store in a "hard coded" physical address and not
in the ACPI table itself.
- ACPI notification is triggered when the GUID is changed.
V6 - include the pre-compiled ASL file
- remove an empty line at end of files.
V5 - Move device's description to SSDT table (dynamic).
V4 - Fix a typo in error message string.
- Move device's description from DSDT back to SSDT table.
V3 - Remove "-uuid" command line parameter.
- Move device's description from SSDT to DSDT table.
- Add new "vmgenid" sysbus device.
Gal Hammer (3):
docs: vm generation id device's description
i386: Add a Virtual Machine Generation ID device
tests: update acpi tables after adding the vmgenid device
default-configs/i386-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
docs/specs/vmgenid.txt | 27 ++++++++
hw/acpi/core.c | 8 +++
hw/acpi/ich9.c | 8 +++
hw/acpi/piix4.c | 8 +++
hw/i386/acpi-build.c | 26 +++++++
hw/i386/acpi-dsdt.dsl | 4 +-
hw/i386/acpi-dsdt.hex.generated | 6 +-
hw/i386/pc.c | 8 +++
hw/i386/q35-acpi-dsdt.dsl | 5 +-
hw/i386/q35-acpi-dsdt.hex.generated | 8 +--
hw/i386/ssdt-misc.dsl | 43 ++++++++++++
hw/i386/ssdt-misc.hex.generated | 8 +--
hw/isa/lpc_ich9.c | 1 +
hw/misc/Makefile.objs | 1 +
hw/misc/vmgenid.c | 131 +++++++++++++++++++++++++++++++++++
include/hw/acpi/acpi.h | 2 +
include/hw/acpi/acpi_dev_interface.h | 4 ++
include/hw/acpi/ich9.h | 2 +
include/hw/i386/pc.h | 3 +
include/hw/misc/vmgenid.h | 21 ++++++
tests/acpi-test-data/pc/DSDT | Bin 2807 -> 2820 bytes
tests/acpi-test-data/pc/SSDT | Bin 3065 -> 3268 bytes
tests/acpi-test-data/q35/DSDT | Bin 7397 -> 7410 bytes
tests/acpi-test-data/q35/SSDT | Bin 1346 -> 1549 bytes
26 files changed, 313 insertions(+), 13 deletions(-)
create mode 100644 docs/specs/vmgenid.txt
create mode 100644 hw/misc/vmgenid.c
create mode 100644 include/hw/misc/vmgenid.h
--
1.9.3
next reply other threads:[~2014-11-16 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 10:15 Gal Hammer [this message]
2014-11-16 10:15 ` [Qemu-devel] [PATCH 1/3] docs: vm generation id device's description Gal Hammer
2014-11-16 10:15 ` [Qemu-devel] [PATCH 2/3] i386: Add a Virtual Machine Generation ID device Gal Hammer
2014-11-16 10:15 ` [Qemu-devel] [PATCH 3/3] tests: update acpi tables after adding the vmgenid device Gal Hammer
2014-11-16 19:49 ` [Qemu-devel] [PATCH V8 0/3] Virtual Machine Generation ID Michael S. Tsirkin
2014-11-17 9:03 ` Gal Hammer
2014-11-17 9:28 ` 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=1416132959-25905-1-git-send-email-ghammer@redhat.com \
--to=ghammer@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).