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