From: Laszlo Ersek <lersek@redhat.com>
To: "Gabriel L. Somlo" <somlo@cmu.edu>
Cc: qemu devel list <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Alexander Graf <agraf@suse.de>,
Anthony Perard <anthony.perard@citrix.com>,
Artyom Tarasenko <atar4qemu@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>,
Eduardo Habkost <ehabkost@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Michael Walle <michael@walle.cc>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 wave 1 0/4] fw-cfg: support writeable blobs and more files
Date: Thu, 12 Jan 2017 11:09:05 +0100 [thread overview]
Message-ID: <17e1323e-f757-c55b-74c3-24b038304e28@redhat.com> (raw)
In-Reply-To: <20170112022510.GA14378@foober.ini.cmu.edu>
On 01/12/17 03:25, Gabriel L. Somlo wrote:
> On Wed, Jan 11, 2017 at 06:34:53PM +0100, Laszlo Ersek wrote:
>> This is the first (fw_cfg) half of the v5 iteration of the series posted
>> here:
>> <http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg00129.html>.
>>
>> In this version, the fw_cfg patches have been separated into a
>> standalone "wave", for helping review / maintenance, and also for
>> enabling independent features on top of writeable blobs. More
>> importantly, I've addressed Igor's v4 feedback. See the individual
>> patches for the details.
>>
>> Patch #3 is included verbatim from Eduardo's pending series (see the
>> patch notes for the archive URL), as a dependency for patch #4. If
>> Eduardo's series is merged first, patch #3 can be dropped (in fact
>> git-rebase should do it automatically).
>>
>> Please excuse the surprisingly long list of CC's, it's due to the fact
>> that fw_cfg is quite widely used (see patch #4).
>>
>> Cc: "Gabriel L. Somlo" <somlo@cmu.edu>
>
> Whole series:
>
> Acked-by: Gabriel Somlo <somlo@cmu.edu>
>
> Data passed in via the "-fw_cfg" qemu command still shows up fine in
> /sys/firmware/qemu-fw-cfg on the guest, so also:
>
> Tested-by: Gabriel Somlo <somlo@cmu.edu>
Thank you!
Laszlo
>
> Thanks,
> --Gabriel
>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>> Cc: Alexander Graf <agraf@suse.de>
>> Cc: Anthony Perard <anthony.perard@citrix.com>
>> Cc: Artyom Tarasenko <atar4qemu@gmail.com>
>> Cc: David Gibson <david@gibson.dropbear.id.au>
>> Cc: Eduardo Habkost <ehabkost@redhat.com>
>> Cc: Gerd Hoffmann <kraxel@redhat.com>
>> Cc: Igor Mammedov <imammedo@redhat.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> Cc: Michael Walle <michael@walle.cc>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Cc: Shannon Zhao <zhaoshenglong@huawei.com>
>> Cc: Stefano Stabellini <sstabellini@kernel.org>
>> Cc: qemu-arm@nongnu.org
>>
>> Thanks
>> Laszlo
>>
>>
>> Eduardo Habkost (1):
>> pc: Add 2.9 machine-types
>>
>> Laszlo Ersek (2):
>> fw-cfg: turn FW_CFG_FILE_SLOTS into a device property
>> fw-cfg: bump "file_slots" to 0x20 for 2.9+ machine types
>>
>> Michael S. Tsirkin (1):
>> fw-cfg: support writeable blobs
>>
>> docs/specs/fw_cfg.txt | 36 ++++++++++----
>> hw/lm32/lm32_hwsetup.h | 2 +-
>> include/hw/compat.h | 10 +++-
>> include/hw/i386/pc.h | 2 +
>> include/hw/loader.h | 7 +--
>> include/hw/nvram/fw_cfg.h | 3 +-
>> include/hw/nvram/fw_cfg_keys.h | 3 +-
>> hw/arm/virt-acpi-build.c | 2 +-
>> hw/core/loader.c | 18 ++++---
>> hw/i386/acpi-build.c | 4 +-
>> hw/i386/pc_piix.c | 15 ++++--
>> hw/i386/pc_q35.c | 13 ++++-
>> hw/nvram/fw_cfg.c | 110 +++++++++++++++++++++++++++++++++++------
>> 13 files changed, 177 insertions(+), 48 deletions(-)
>>
>> --
>> 2.9.3
>>
next prev parent reply other threads:[~2017-01-12 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:34 [Qemu-devel] [PATCH v5 wave 1 0/4] fw-cfg: support writeable blobs and more files Laszlo Ersek
2017-01-11 17:34 ` [Qemu-devel] [PATCH v5 wave 1 1/4] fw-cfg: support writeable blobs Laszlo Ersek
2017-01-11 17:34 ` [Qemu-devel] [PATCH v5 wave 1 2/4] fw-cfg: turn FW_CFG_FILE_SLOTS into a device property Laszlo Ersek
2017-01-12 13:10 ` Eduardo Habkost
2017-01-12 16:30 ` Laszlo Ersek
2017-01-12 16:45 ` Eduardo Habkost
2017-01-12 14:29 ` Michael S. Tsirkin
2017-01-12 16:34 ` Laszlo Ersek
2017-01-11 17:34 ` [Qemu-devel] [PATCH v5 wave 1 3/4] pc: Add 2.9 machine-types Laszlo Ersek
2017-01-11 17:34 ` [Qemu-devel] [PATCH v5 wave 1 4/4] fw-cfg: bump "file_slots" to 0x20 for 2.9+ machine types Laszlo Ersek
2017-01-12 2:25 ` [Qemu-devel] [PATCH v5 wave 1 0/4] fw-cfg: support writeable blobs and more files Gabriel L. Somlo
2017-01-12 10:09 ` Laszlo Ersek [this message]
2017-01-12 14:30 ` Michael S. Tsirkin
2017-01-12 16:37 ` 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=17e1323e-f757-c55b-74c3-24b038304e28@redhat.com \
--to=lersek@redhat.com \
--cc=agraf@suse.de \
--cc=anthony.perard@citrix.com \
--cc=atar4qemu@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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=somlo@cmu.edu \
--cc=sstabellini@kernel.org \
--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).