From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ed Swierk <eswierk@skyportsystems.com>
Cc: qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] Virtual Machine Generation ID
Date: Fri, 16 Sep 2016 03:36:55 +0300 [thread overview]
Message-ID: <20160916033402-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAO_EM_kuP9kk55bzxWqNOeuL8yW7gKNnacd1-UVGnJPyx2ZNYw@mail.gmail.com>
On Thu, Sep 15, 2016 at 05:23:28PM -0700, Ed Swierk wrote:
> I'm wondering what it will take to finish up work on vmgenid.
>
> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05599.html
>
> It appears all of the designs explored through the 19 iterations were
> problematic in some way. Is any of them vaguely acceptable to all
> involved in the discussions? Or do we need to start from square one?
>
> --Ed
We have ACPI_BUILD_TPMLOG_FILE in tree now and I think it could be
allocated in a similar way.
Integrate patch "fw-cfg: support writeable blobs" to communicate the
allocated address back to QEMU.
--
MST
next prev parent reply other threads:[~2016-09-16 0:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 0:23 [Qemu-devel] Virtual Machine Generation ID Ed Swierk
2016-09-16 0:36 ` Michael S. Tsirkin [this message]
2016-10-04 22:51 ` Ed Swierk
2016-10-05 9:45 ` Igor Mammedov
2016-10-06 1:29 ` Michael S. Tsirkin
2016-12-07 2:15 ` Ben Warren
2016-12-11 3:28 ` Michael S. Tsirkin
2017-01-15 6:17 ` Ben Warren
2017-01-16 8:47 ` Igor Mammedov
2017-01-16 14:21 ` Michael S. Tsirkin
2017-01-16 18:57 ` Ben Warren
2017-01-17 13:26 ` Igor Mammedov
2017-01-17 14:26 ` Ed Swierk
2017-01-17 14:33 ` Michael S. Tsirkin
2017-01-17 15:01 ` Ed Swierk
2017-01-17 15:21 ` Michael S. Tsirkin
2017-01-17 17:35 ` Ben Warren
2017-01-17 16:24 ` Igor Mammedov
2017-01-17 17:42 ` Michael S. Tsirkin
2017-01-17 17:45 ` Michael S. Tsirkin
2017-01-19 0:02 ` Ben Warren
2017-01-19 7:09 ` Ben Warren
2017-01-19 9:25 ` Laszlo Ersek
2017-01-19 17:47 ` Ben Warren
2017-01-19 18:20 ` Laszlo Ersek
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=20160916033402-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eswierk@skyportsystems.com \
--cc=imammedo@redhat.com \
--cc=lersek@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.