This is part of the ongoing effort to make Secure Boot for aarch64
libvirt guests possible[1].

I'd be happy to have the QAPI experts debunk my claim that there is
no semantically-meaningful way to represent this; in the meantime,
I'll be posting very shortly some libvirt patches that IMO prove that
supporting what I'm proposing here does not impose a significant
burden on consumers of the firmware descriptors.

[1] https://issues.redhat.com/browse/RHEL-82645

Andrea Bolognani (2):
  docs/interop/firmware: Rename FirmwareFormat to FirmwareFlashFormat
  docs/interop/firmware: Introduce extended syntax for
    FirmwareMappingMemory

 docs/interop/firmware.json | 192 +++++++++++++++++++++++++++++++++++--
 1 file changed, 184 insertions(+), 8 deletions(-)

-- 
2.52.0

On Mon, Dec 29, 2025 at 12:26:47AM +0100, Andrea Bolognani wrote:
> This is part of the ongoing effort to make Secure Boot for aarch64
> libvirt guests possible[1].
> 
> I'd be happy to have the QAPI experts debunk my claim that there is
> no semantically-meaningful way to represent this; in the meantime,
> I'll be posting very shortly some libvirt patches that IMO prove that
> supporting what I'm proposing here does not impose a significant
> burden on consumers of the firmware descriptors.

Series looks sane to me, and I think you are correct although I wouldn't
claim myself being a QAPI expert.

take care,
  Gerd

On Mon, Dec 29, 2025 at 12:26:47AM +0100, Andrea Bolognani wrote:
> This is part of the ongoing effort to make Secure Boot for aarch64
> libvirt guests possible[1].
>
> I'd be happy to have the QAPI experts debunk my claim that there is
> no semantically-meaningful way to represent this; in the meantime,
> I'll be posting very shortly some libvirt patches that IMO prove that
> supporting what I'm proposing here does not impose a significant
> burden on consumers of the firmware descriptors.

The patch that extends the parser to support the new syntax is [2];
the patch series, for context, is [3].

Note that the libvirt list server is acting wonky right now, so you
might want to use alternative URLs (e.g. [4] and [5]) instead.


[1] https://issues.redhat.com/browse/RHEL-82645
[2] https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/message/VKZQUHGGLKP3YWX5FCY4UUVME4ZOIS34/
[3] https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/TGLFMPRXCATRPA6MPHH5KYXY5XCTSRDT/
[4] https://www.mail-archive.com/devel@lists.libvirt.org/msg13963.html
[5] https://www.mail-archive.com/devel@lists.libvirt.org/msg13955.html
-- 
Andrea Bolognani / Red Hat / Virtualization