From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: ben@skyportsystems.com, qemu-devel@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/6] ACPI: Add Virtual Machine Generation ID support
Date: Tue, 17 Jan 2017 17:37:14 +0100 [thread overview]
Message-ID: <6bbd752d-d354-808e-81c6-2aa270997538@redhat.com> (raw)
In-Reply-To: <20170117163848-mutt-send-email-mst@kernel.org>
On 01/17/17 15:41, Michael S. Tsirkin wrote:
> On Tue, Jan 17, 2017 at 02:00:58PM +0100, Igor Mammedov wrote:
>> Question is how you'd get address of it and I think that's where
>> writable fwcfg files come in play.
>> I'd prefer fwcfg_loader in firmware to write it back after buffer
>> allocation is done as it's already has utilities for fw_cfg,
>> but that probably would mean extending loader protocol to support
>> new writeback command.
>
> Right. It's quite easy to do as at least seabios was written to
> ignore commands it does not recognize. So with old bios you
> just don't get a write. Not sure about UEFI, worth checking.
Same; OVMF skips (and logs) unknown commands.
>
>> PS, address one would get from guest should be migrated as well
>
> IIRC writeable fw cfg blobs are migrated automatically.
>
When added with rom_add_blob() or derivative functions / function-like
macros, they are.
Thanks
Laszlo
next prev parent reply other threads:[~2017-01-17 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:20 [Qemu-devel] [PATCH v2 0/6] Add support for VM Generation ID ben
[not found] ` <cover.1484594095.git.ben@skyportsystems.com>
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 1/6] docs: vm generation id device's description ben
2017-01-16 19:51 ` Eric Blake
2017-01-16 20:08 ` Ben Warren
2017-01-16 21:20 ` Eric Blake
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 2/6] ACPI: Add a function for building named qword entries ben
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 3/6] ACPI: Add Virtual Machine Generation ID support ben
2017-01-17 13:00 ` Igor Mammedov
2017-01-17 13:18 ` Laszlo Ersek
2017-01-17 14:41 ` Michael S. Tsirkin
2017-01-17 16:37 ` Laszlo Ersek [this message]
2017-01-18 0:23 ` Ben Warren
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 4/6] qmp/hmp: add query-vm-generation-id and 'info vm-generation-id' commands ben
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 5/6] qmp/hmp: add set-vm-generation-id commands ben
2017-01-18 8:55 ` Igor Mammedov
2017-01-18 22:14 ` Ben Warren
2017-01-16 19:20 ` [Qemu-devel] [PATCH v2 6/6] PC: Support dynamic sysbus on pc_i440fx ben
2017-01-18 8:46 ` 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=6bbd752d-d354-808e-81c6-2aa270997538@redhat.com \
--to=lersek@redhat.com \
--cc=ben@skyportsystems.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@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).