All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Kashyap Chamarthy" <kchamart@redhat.com>
Subject: Re: [PATCH v2 4/4] docs/firmware: add feature flag for qemu variable store
Date: Wed, 19 Mar 2025 11:07:05 +0000	[thread overview]
Message-ID: <Z9qlWV_TsnndwIM4@redhat.com> (raw)
In-Reply-To: <20250319110152.1309969-5-kraxel@redhat.com>

On Wed, Mar 19, 2025 at 12:01:51PM +0100, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>  docs/interop/firmware.json | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json
> index 57f55f6c5455..76df1043dae9 100644
> --- a/docs/interop/firmware.json
> +++ b/docs/interop/firmware.json
> @@ -214,13 +214,16 @@
>  #                  PL011 UART. @verbose-static is mutually exclusive
>  #                  with @verbose-dynamic.
>  #
> +# @qemu-vars: The firmware expects qemu to provide an efi variable
> +#             store, via "uefi-vars-sysbus" or "uefi-vars-x64" device.

It seems like this would imply mapping.device == memory, as if we had
mapping.device == flash, then we would need to extend FirmwareFlashMode
with an extra option ? If so, lets document this expectation.

> +#
>  # Since: 3.0
>  ##
>  { 'enum' : 'FirmwareFeature',
>    'data' : [ 'acpi-s3', 'acpi-s4',
>               'amd-sev', 'amd-sev-es', 'amd-sev-snp',
>               'intel-tdx',
> -             'enrolled-keys', 'requires-smm', 'secure-boot',
> +             'enrolled-keys', 'requires-smm', 'secure-boot', 'qemu-vars',
>               'verbose-dynamic', 'verbose-static' ] }
>  
>  ##
> -- 
> 2.48.1
> 

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-03-19 11:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 11:01 [PATCH v2 0/4] [for-10.0] hw/uefi: some bugfixes Gerd Hoffmann
2025-03-19 11:01 ` [PATCH v2 1/4] hw/uefi: flush variable store to disk in post load Gerd Hoffmann
2025-03-19 11:57   ` Philippe Mathieu-Daudé
2025-03-19 11:01 ` [PATCH v2 2/4] hw/uefi: fix error handling in uefi_vars_json_save Gerd Hoffmann
2025-03-19 11:58   ` Philippe Mathieu-Daudé
2025-03-19 11:01 ` [PATCH v2 3/4] hw/uefi: fix error handling in uefi_vars_json_load Gerd Hoffmann
2025-03-19 11:59   ` Philippe Mathieu-Daudé
2025-03-19 11:01 ` [PATCH v2 4/4] docs/firmware: add feature flag for qemu variable store Gerd Hoffmann
2025-03-19 11:07   ` Daniel P. Berrangé [this message]
2025-03-19 11:30     ` Gerd Hoffmann
2025-03-19 11:37       ` Daniel P. Berrangé
2025-03-19 11:51         ` Gerd Hoffmann
2025-03-19 12:20           ` Daniel P. Berrangé
2025-03-19 13:03             ` Gerd Hoffmann
2025-03-19 13:15               ` Daniel P. Berrangé

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=Z9qlWV_TsnndwIM4@redhat.com \
    --to=berrange@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.