From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: ghammer@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH V14 0/3] Virtual Machine Generation ID
Date: Tue, 3 Mar 2015 17:18:12 +0100 [thread overview]
Message-ID: <1425399495-13664-1-git-send-email-imammedo@redhat.com> (raw)
Changes since v13:
* fix comment style to /*... */ in testcase
* make BAR TARGET_PAGE_SIZE as required by spec
* make BAR prefetchable, spec also says that it shouldn't be
marked as non cached
* ACPI part
* merge separate VGID device with PCI device description
* mark device as not shown in UI,
it hides "VM Generation ID" device from device manager
and leaves only "PCI Standard RAM Controller" device there
Note to maintainer:
this patch set doesn't include the *.hex.generated files and
updated test ACPI tables blobs. Hex files for [q35-]acpi-dsdt
should be updated.
Tested with WS2012R2DCx64, thanks Gal for providing test utilities.
Based on top of mst's PCI tree.
Git branch:
https://github.com/imammedo/qemu.git vmgenid_v14
Gal Hammer (1):
docs: vm generation id device's description
Igor Mammedov (2):
pc: add a Virtual Machine Generation ID device
tests: add a unit test for the vmgenid device.
default-configs/i386-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
docs/specs/pci-ids.txt | 1 +
docs/specs/vmgenid.txt | 36 ++++++++++
hw/i386/acpi-build.c | 69 +++++++++++++++++--
hw/i386/acpi-dsdt.dsl | 2 -
hw/i386/q35-acpi-dsdt.dsl | 2 -
hw/misc/Makefile.objs | 1 +
hw/misc/vmgenid.c | 134 +++++++++++++++++++++++++++++++++++++
include/hw/acpi/acpi.h | 1 +
include/hw/misc/vmgenid.h | 21 ++++++
include/hw/pci/pci.h | 1 +
tests/Makefile | 2 +
tests/vmgenid-test.c | 92 +++++++++++++++++++++++++
14 files changed, 356 insertions(+), 8 deletions(-)
create mode 100644 docs/specs/vmgenid.txt
create mode 100644 hw/misc/vmgenid.c
create mode 100644 include/hw/misc/vmgenid.h
create mode 100644 tests/vmgenid-test.c
--
2.1.0
next reply other threads:[~2015-03-03 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:18 Igor Mammedov [this message]
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 1/3] docs: vm generation id device's description Igor Mammedov
2015-03-04 19:57 ` Eric Blake
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 2/3] pc: add a Virtual Machine Generation ID device Igor Mammedov
2015-03-03 17:35 ` Michael S. Tsirkin
2015-03-03 20:33 ` Igor Mammedov
2015-03-04 12:11 ` Michael S. Tsirkin
2015-03-04 13:12 ` Igor Mammedov
2015-03-04 13:49 ` Michael S. Tsirkin
2015-03-04 14:03 ` Andreas Färber
2015-03-04 15:14 ` Igor Mammedov
2015-03-04 15:31 ` Michael S. Tsirkin
2015-03-04 16:33 ` Igor Mammedov
2015-03-04 19:12 ` Michael S. Tsirkin
2015-03-05 14:22 ` Igor Mammedov
2015-03-11 5:35 ` David Gibson
2015-03-19 9:50 ` Michael S. Tsirkin
2015-03-19 11:31 ` Gal Hammer
2015-03-20 4:58 ` David Gibson
2015-03-03 16:18 ` [Qemu-devel] [PATCH V14 3/3] tests: add a unit test for the vmgenid device Igor Mammedov
2015-04-15 10:38 ` [Qemu-devel] [PATCH V14 0/3] Virtual Machine Generation ID Michael S. Tsirkin
2015-04-15 13:59 ` Igor Mammedov
2015-04-19 7:52 ` Michael S. Tsirkin
2015-04-19 13:38 ` Yan Vugenfirer
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=1425399495-13664-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=ghammer@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 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).