qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gal Hammer <ghammer@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 15:40:45 +0200	[thread overview]
Message-ID: <54159ADD.10200@redhat.com> (raw)
In-Reply-To: <54157317.3040208@redhat.com>

Il 14/09/2014 12:51, Gal Hammer ha scritto:
>>
>> 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?

I said you have to either:

1) Use the DSDT, with a dynamic _STA method.

2) Use the SSDT, and only add the device if the device is specified on
the command line.  This avoids the avoid migration issues.  At this
point the _STA method can be static.

Using the DSDT is possible, it's just that you have to do it as well for
Q35, and I think it is harder than moving it back to the SSDT.  Sorry
for not thinking earlier about the different chipsets.

Paolo

      reply	other threads:[~2014-09-14 13:41 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
2014-09-14 13:40     ` Paolo Bonzini [this message]

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=54159ADD.10200@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@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).