From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
"Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, Michael Walle <michael@walle.cc>,
Kevin O'Connor <kevin@koconnor.net>,
qemu-arm@nongnu.org, Shannon Zhao <zhaoshenglong@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH RFC] fw-cfg: support writeable blobs
Date: Tue, 23 Feb 2016 08:07:17 +0100 [thread overview]
Message-ID: <1456211237.29896.72.camel@redhat.com> (raw)
In-Reply-To: <20160222220400-mutt-send-email-mst@redhat.com>
On Mo, 2016-02-22 at 22:12 +0200, Michael S. Tsirkin wrote:
> On Mon, Feb 22, 2016 at 03:26:56PM +0100, Gerd Hoffmann wrote:
> > On Mo, 2016-02-22 at 14:41 +0200, Michael S. Tsirkin wrote:
> > > Useful to send guest data back to QEMU.
> >
> > Use case?
> >
> > cheers,
> > Gerd
>
> VM GEN ID at least wants to pass address of some blob
> in guest memory to host.
>
> Apparently, that's also useful for nvdimm.
>
> A reasonable way to do that seems to be to write it into
> fw cfg file, this way it's also migrated automatically.
Both seem to be about acpi aml code talking to qemu backend.
Not sure fw_cfg files are reasonable for that, given that you have to
fetch the directory listing, parse it to figure the entry index, ...
I want see a patch actually using that before going to merge it.
cheers,
Gerd
next prev parent reply other threads:[~2016-02-23 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:41 [Qemu-devel] [PATCH RFC] fw-cfg: support writeable blobs Michael S. Tsirkin
2016-02-22 14:26 ` Gerd Hoffmann
2016-02-22 20:12 ` Michael S. Tsirkin
2016-02-23 7:07 ` Gerd Hoffmann [this message]
2016-02-23 9:09 ` Michael S. Tsirkin
2016-02-22 14:47 ` Kevin O'Connor
2016-02-22 19:15 ` Michael S. Tsirkin
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=1456211237.29896.72.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=kevin@koconnor.net \
--cc=michael@walle.cc \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=somlo@cmu.edu \
--cc=zhaoshenglong@huawei.com \
/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).