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 13:15:41 +0000	[thread overview]
Message-ID: <Z9rDfbm5vw-uTVJJ@redhat.com> (raw)
In-Reply-To: <rjz4px5v7csjjo5vehhgpotbwjf6fptkexcyv5jg7omwgdtl7h@cnhgtnyjk4ly>

On Wed, Mar 19, 2025 at 02:03:09PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > > > There is 'stateless' already for 'firmware image in r/o flash'.
> > > > 
> > > > What's the behaviour of UEFI if build with JSON vars support, but without
> > > > QEMU providing any JSON vars backend ?
> > > 
> > > It will panic.
> > 
> > In that case, we must not reuse 'stateless' with such builds, as that's
> > quite different semantics & incompatible with current usage.
> > 
> > We would need a new 'uefi-vars' mode, or just declare that we must
> > always use 'memory'  not 'flash' for such builds.
> 
> I don't see how 'flash.stateless' is any different than 'memory' (or
> 'kernel', or maybe 'igvm' some day).  If the 'host-uefi-vars' feature
> is present '-device uefi-vars-$kind' is required, no matter how you
> load the firmware.
> 
> What exactly will an old libvirt which does not know the
> 'host-uefi-vars' feature do in case it finds a firmware.json file with
> that feature?  Play safe and ignore the file?

No, unknown features are simply ignored. 

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 13:16 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é
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é [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=Z9rDfbm5vw-uTVJJ@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.