qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gal Hammer <ghammer@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH RESEND 0/2 V2] Virtual Machine Generation ID
Date: Sun, 14 Sep 2014 13:51:03 +0300	[thread overview]
Message-ID: <54157317.3040208@redhat.com> (raw)
In-Reply-To: <54155656.4000200@redhat.com>

On 14/09/2014 11:48, Paolo Bonzini wrote:
> Il 14/09/2014 08:25, Gal Hammer ha scritto:
>> Hi,
>>
>> A two parts patch to add a QEmu support for Microsoft's Virtual Machine
>> Generation ID device.
>>
>> The first one add a new ACPI directive which allow to use a 16-bytes
>> buffer in an ACPI table. This buffer is for storing the VM's UUID.
>>
>> The second is the ACPI tables changes and the actual device.
>>
>> Your comment are welcomed.
>>
>> Thanks,
>>
>>      Gal.
>>
>> V2: - Remove "-uuid" command line parameter.
>>      - Move device's description from SSDT to DDST table.
>>      - Add new "vmgenid" sysbus device.
>>
>> Gal Hammer (2):
>>    i386: Add an ACPI_EXTRACT_NAME_BUFFER16 directive.
>>    i386: Add a Virtual Machine Generation ID device.
>>
>>   default-configs/i386-softmmu.mak   |  1 +
>>   default-configs/x86_64-softmmu.mak |  1 +
>>   hw/i386/acpi-build.c               | 23 ++++++++++-
>>   hw/i386/acpi-dsdt.dsl              | 37 +++++++++++++++++
>>   hw/misc/Makefile.objs              |  1 +
>>   hw/misc/vmgenid.c                  | 85 ++++++++++++++++++++++++++++++++++++++
>>   include/hw/i386/pc.h               |  3 ++
>>   scripts/acpi_extract.py            | 23 +++++++----
>>   8 files changed, 163 insertions(+), 11 deletions(-)
>>   create mode 100644 hw/misc/vmgenid.c
>>
>
> The idea is okay, but the device has to be added to the Q35 DSDT as
> well.  If you just #included a file in the same style as
> acpi-dsdt-hpet.dsl, you would have a namespace clash between the PIIX
> and Q35 DSDTs.  acpi-dsdt-hpet.dsl can do it because it has no
> ACPI_EXTRACT directives.
>
> I think because of this, it is a bit simpler to add the device
> optionally to the SSDT, similar to how the TPM is handled.

Back to SSDT? Didn't you say something about migration issues that 
prevent me from using SSDT because the table's data is modified?

>
> Paolo
>

     Gal.

  reply	other threads:[~2014-09-14 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14  6:25 [Qemu-devel] [PATCH RESEND 0/2 V2] Virtual Machine Generation ID Gal Hammer
2014-09-14  6:25 ` [Qemu-devel] [PATCH 1/2] i386: Add an ACPI_EXTRACT_NAME_BUFFER16 directive Gal Hammer
2014-09-14  8:48   ` Paolo Bonzini
2014-09-14  6:25 ` [Qemu-devel] [PATCH 2/2] i386: Add a Virtual Machine Generation ID device Gal Hammer
2014-09-14  8:48 ` [Qemu-devel] [PATCH RESEND 0/2 V2] Virtual Machine Generation ID Paolo Bonzini
2014-09-14 10:51   ` Gal Hammer [this message]
2014-09-14 13:40     ` Paolo Bonzini

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=54157317.3040208@redhat.com \
    --to=ghammer@redhat.com \
    --cc=armbru@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).