From: Laszlo Ersek <lersek@redhat.com>
To: libvirt devel <libvir-list@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>
Cc: Thomas Huth <thuth@redhat.com>,
Kashyap Chamarthy <kchamart@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] [qemu PATCH] docs/interop: add "firmware.json"
Date: Wed, 9 May 2018 17:18:45 +0200 [thread overview]
Message-ID: <682d4d57-35d2-6eb0-766c-cba4819ef05a@redhat.com> (raw)
In-Reply-To: <20180509150431.4979-1-lersek@redhat.com>
On 05/09/18 17:04, Laszlo Ersek wrote:
> Add a schema that describes the different uses and properties of virtual
> machine firmware.
>
> Each firmware executable installed on a host system should come with at
> least one JSON file that conforms to this schema. Each file informs the
> management applications about
> - the firmware's properties and one possible use case / feature set,
> - configuration bits that are required to run the firmware binary.
>
> In addition, define rules for management apps for picking the highest
> priority firmware JSON file when multiple such files match the search
> criteria.
>
> Cc: "Daniel P. Berrange" <berrange@redhat.com>
> Cc: David Gibson <dgibson@redhat.com>
> Cc: Eric Blake <eblake@redhat.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Kashyap Chamarthy <kchamart@redhat.com>
> Cc: Markus Armbruster <armbru@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
>
> Notes:
> PATCH:
>
> - previous version (RFCv3) was posted at:
> <http://mid.mail-archive.com/20180420231246.23130-4-lersek@redhat.com>
>
> - move "firmware.json" under docs/interop/; drop earlier development
> artifacts
>
> - no changes to the schema (received no comments on RFCv3)
oops:
> +##
> +# @x-check-firmware:
> +#
> +# Accept a @Firmware object and do nothing, successfully. This command
> +# can be used in the QMP shell to validate @Firmware JSON against the
> +# schema.
> +#
> +# @fw: ignored
> +#
> +# Since: 2.13
> +##
> +{ 'command' : 'x-check-firmware',
> + 'data' : { 'fw' : 'Firmware' } }
>
missed this part (I should have removed it), I will post v2 soon.
Laszlo
prev parent reply other threads:[~2018-05-09 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:04 [Qemu-devel] [qemu PATCH] docs/interop: add "firmware.json" Laszlo Ersek
2018-05-09 15:18 ` Laszlo Ersek [this message]
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=682d4d57-35d2-6eb0-766c-cba4819ef05a@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=dgibson@redhat.com \
--cc=kchamart@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).