From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: jordan.l.justen@intel.com, qemu-devel@nongnu.org,
gleb@cloudius-systems.com
Subject: Re: [Qemu-devel] fw_cfg specification ?
Date: Thu, 12 Mar 2015 15:17:12 +0100 [thread overview]
Message-ID: <55019FE8.1020706@redhat.com> (raw)
In-Reply-To: <5500B3E1.8020402@redhat.com>
On 11/03/2015 22:30, Laszlo Ersek wrote:
> In any case, I'm unaware of *any* instance when an fw_cfg blob is
> rewritten by the guest.
>
> In fact, such *write* callbacks are registered in qemu with
> fw_cfg_add_callback(), and I can't see any calls to that function. It's
> dead code, apparently.
Let's nuke it. :)
Paolo
next prev parent reply other threads:[~2015-03-12 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 15:27 [Qemu-devel] fw_cfg specification ? Gabriel L. Somlo
2015-03-11 18:50 ` Laszlo Ersek
2015-03-11 20:45 ` Gabriel L. Somlo
2015-03-11 21:30 ` Laszlo Ersek
2015-03-12 7:47 ` Gerd Hoffmann
2015-03-12 14:17 ` Paolo Bonzini [this message]
2015-03-12 15:42 ` Laszlo Ersek
2015-03-12 16:16 ` Gabriel L. Somlo
2015-03-12 16:35 ` Paolo Bonzini
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=55019FE8.1020706@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@cloudius-systems.com \
--cc=gsomlo@gmail.com \
--cc=jordan.l.justen@intel.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 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).