All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Gal Hammer <ghammer@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, imammedo@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V16 1/4] docs: vm generation id device's description
Date: Tue, 16 Jun 2015 09:22:28 -0600	[thread overview]
Message-ID: <55803F34.9050203@redhat.com> (raw)
In-Reply-To: <1434463863-26560-2-git-send-email-ghammer@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2759 bytes --]

On 06/16/2015 08:11 AM, Gal Hammer wrote:
> Signed-off-by: Gal Hammer <ghammer@redhat.com>
> ---
>  docs/specs/vmgenid.txt | 33 +++++++++++++++++++++++++++++++++
>  1 file changed, 33 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..d06977a
> --- /dev/null
> +++ b/docs/specs/vmgenid.txt
> @@ -0,0 +1,33 @@
> +VIRTUAL MACHINE GENERATION ID
> +=============================
> +
> +Copyright (C) 2015 Red Hat, Inc.
> +
> +This work is licensed under the terms of the GNU GPL, version 2 or later.
> +See the COPYING file in the top-level directory.
> +
> +===
> +
> +The VM generation ID (vmgenid) device is an emulated device which
> +is expected to exposes a 128-bit, cryptographically random, integer value

s/exposes/expose/

> +identifier, provided by a management system (It is NOT in the device's
> +responsibilty to ensure that the value is cryptographically random).

s/responsibilty/responsibility/

> +
> +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).
> +
> +This is specified on the web at: http://go.microsoft.com/fwlink/?LinkId=260709
> +

Hopefully the link doesn't go stale too soon (when the cover page states
the same address, and the disclaimer "Information ... in this document,
URL and other Internet website references, may change without notice").
 On the other hand, the document is fairly loosely licensed ("You may
copy and use this document for your internal, reference purposes") even
if done in a non-free .docx format.  Do we need to hedge our bets and
save a copy of it in the qemu wiki?

> +---
> +
> +The vmgenid device is a device with the following ACPI ID: "QEMU0002".
> +
> +It has two properties:
> +
> +uuid - The virtual machine generation ID (A required UUID string)
> +addr - The uuid memory location (A 64-bit address, defaults to 0xfedf0000)
> +
> +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.

Still would be nice for this document to contain sample QMP commands for
getting at the QOM object necessary for changing the id exposed to the
guest via this device (that is, not only talk about how the device is
implemented in the ACPI view of the guest, but also how the device is
managed from the application driving qemu).

-- 
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: 604 bytes --]

  reply	other threads:[~2015-06-16 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 14:10 [Qemu-devel] [PATCH V16 0/4] Virtual Machine Generation ID Gal Hammer
2015-06-16 14:11 ` [Qemu-devel] [PATCH V16 1/4] docs: vm generation id device's description Gal Hammer
2015-06-16 15:22   ` Eric Blake [this message]
2015-06-16 14:11 ` [Qemu-devel] [PATCH V16 2/4] acpi: add a vm_generation_id_changed method Gal Hammer
2015-06-16 15:23   ` Eric Blake
2015-06-16 22:55   ` Igor Mammedov
2015-06-16 14:11 ` [Qemu-devel] [PATCH V16 3/4] i386: add a Virtual Machine Generation ID device Gal Hammer
2015-06-16 22:52   ` Igor Mammedov
2015-06-16 23:08   ` Igor Mammedov
2015-06-16 14:11 ` [Qemu-devel] [PATCH V16 4/4] tests: add a unit test for the vmgenid device Gal Hammer
2015-06-16 23:41   ` Igor Mammedov

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=55803F34.9050203@redhat.com \
    --to=eblake@redhat.com \
    --cc=ghammer@redhat.com \
    --cc=imammedo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.