From: Eric Blake <eblake@redhat.com>
To: Gal Hammer <ghammer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V9 1/3] docs: vm generation id device's description
Date: Tue, 09 Dec 2014 10:50:07 -0700 [thread overview]
Message-ID: <5487364F.9070000@redhat.com> (raw)
In-Reply-To: <1418141689-10828-2-git-send-email-ghammer@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
On 12/09/2014 09:14 AM, Gal Hammer wrote:
> Signed-off-by: Gal Hammer <ghammer@redhat.com>
>
> ---
> docs/specs/vmgenid.txt | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 docs/specs/vmgenid.txt
>
> diff --git a/docs/specs/vmgenid.txt b/docs/specs/vmgenid.txt
> new file mode 100644
> index 0000000..9a09d11
> --- /dev/null
> +++ b/docs/specs/vmgenid.txt
> @@ -0,0 +1,27 @@
> +VIRTUAL MACHINE GENERATION ID
Just because we aren't consistent doesn't mean that new files can get
away with not listing a license/copyright notice. Check some of the
other recent doc additions for ideas on how to do it concisely.
> +=============================
> +
> +The VM generation ID (vmgenid) device is an emulated device which
> +expose a 128-bit, cryptographically random, integer value identifier.
s/expose/exposes/
> +This allows management applications (e.g. libvirt) to notify the guest
> +operating system when the virtual machine is executed with a different
> +configuration (e.g. snapshot execution or creation from a template).
> +
> +Specs is on the web at: http://go.microsoft.com/fwlink/?LinkId=260709
s/Specs is/This is specified/
> +
> +---
> +
> +The vmgenid device is a sysbus device with the following ACPI ID:
> +"QEMU0002".
> +
> +The device adds a "vmgenid.uuid" property, which can be modifed using
s/modifed/modified/
> +the -global command line argument or the QMP interface.
> +
> +The device uses a fixed memory resource: 0xfedf0000-0xfedf0003. The
What endianness is the memory resource? Is 4 bytes sufficient, or should
it be 8 bytes because it holds a pointer? Or is the size dependent on
the guest hardware?
> +guest is expected to write the physical address of the GUID's buffer
> +to that memory resource. This allows the device to modify the GUID if
> +requested by the management application.
What endianness is the GUID buffer?
> +
> +According to the specification, any change to the GUID executes an
> +ACPI notification. The vmgenid device triggers the GPE._E00 which
> +executes the ACPI Notify operation.
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-12-09 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 16:14 [Qemu-devel] [PATCH V9 0/3] Virtual Machine Generation ID Gal Hammer
2014-12-09 16:14 ` [Qemu-devel] [PATCH V9 1/3] docs: vm generation id device's description Gal Hammer
2014-12-09 17:50 ` Eric Blake [this message]
2014-12-10 15:41 ` Gal Hammer
2014-12-09 16:14 ` [Qemu-devel] [PATCH V9 2/3] i386: Add a Virtual Machine Generation ID device Gal Hammer
2014-12-09 16:14 ` [Qemu-devel] [PATCH V9 3/3] tests: add a unit test for the vmgenid device Gal Hammer
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=5487364F.9070000@redhat.com \
--to=eblake@redhat.com \
--cc=ghammer@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).