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: Thu, 6 Oct 2016 04:29:56 +0300 [thread overview]
Message-ID: <20161006041949-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAO_EM_mHyC7cywV4KUqH_MWwt2vVkK6GEOuaUX0FHpffdfaAuQ@mail.gmail.com>
On Tue, Oct 04, 2016 at 03:51:40PM -0700, Ed Swierk wrote:
> On Thu, Sep 15, 2016 at 5:36 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > 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
> >
> > 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.
>
> Starting with Igor's last version at
> https://github.com/imammedo/qemu/commits/vmgen_wip , it's not clear to
> me which changes need to be ported, which changes are obsoleted by
> your new fw-cfg stuff and/or upstream churn in ACPI, device
> properties, etc. In particular ACPI is still a total mystery to me,
> though passing a single address from guest to host can't be that hard,
> can it?
>
> Any clues would be appreciated.
>
> --Ed
It might be best to just re-start from the beginning.
So the idea is that ACPI should be about supplying the address
to guest. To supply address to host we'll use fw cfg.
This would be new I think:
- add support for writeable fw cfg blobs
- add linker/loader command to write address of a blob into
such a fw cfg file
- add a new file used for vm gen id, use loader command above
to pass the address of a blob allocated for it to host
- whenever vm gen id changes, update file, if we have address
of blob update that as well
- use linker to patch address of blob into acpi as well
it needs to be in a separate ssdt at top level
otherwise it's hard to figure out the offset.
This can be reused from one of the previus versions:
- command line, interrupts and commands to update vm gen id
I can help with acpi if all the rest is clear.
--
MST
next prev parent reply other threads:[~2016-10-06 1:30 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
2016-10-04 22:51 ` Ed Swierk
2016-10-05 9:45 ` Igor Mammedov
2016-10-06 1:29 ` Michael S. Tsirkin [this message]
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=20161006041949-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.