From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Bibo Mao" <maobibo@loongson.cn>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Song Gao" <gaosong@loongson.cn>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-riscv@nongnu.org,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>
Subject: [PATCH v3 6/6] docs/firmware: add feature flag for host uefi variable store
Date: Wed, 19 Mar 2025 15:11:58 +0100 [thread overview]
Message-ID: <20250319141159.1461621-7-kraxel@redhat.com> (raw)
In-Reply-To: <20250319141159.1461621-1-kraxel@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
docs/interop/firmware.json | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json
index 57f55f6c5455..745d21d82232 100644
--- a/docs/interop/firmware.json
+++ b/docs/interop/firmware.json
@@ -214,13 +214,23 @@
# PL011 UART. @verbose-static is mutually exclusive
# with @verbose-dynamic.
#
+# @host-uefi-vars: The firmware expects the host to provide an uefi
+# variable store. qemu supports that via
+# "uefi-vars-sysbus" (aarch64, riscv64, loongarch64)
+# or "uefi-vars-x64" (x86_64) devices. The firmware
+# will not use flash for nvram. When loading the
+# firmware into flash the 'stateless' setup should be
+# used. It is recommened to load the firmware into
+# memory though.
+#
# 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', 'host-uefi-vars',
'verbose-dynamic', 'verbose-static' ] }
##
--
2.48.1
next prev parent reply other threads:[~2025-03-19 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 14:11 [PATCH v3 0/6] [for-10.0] hw/uefi: some bugfixes Gerd Hoffmann
2025-03-19 14:11 ` [PATCH v3 1/6] hw/uefi: flush variable store to disk in post load Gerd Hoffmann
2025-03-19 14:11 ` [PATCH v3 2/6] hw/uefi: fix error handling in uefi_vars_json_save Gerd Hoffmann
2025-03-19 14:11 ` [PATCH v3 3/6] hw/uefi: fix error handling in uefi_vars_json_load Gerd Hoffmann
2025-03-19 14:11 ` [PATCH v3 4/6] hw/uefi-vars-sysbus: allow for riscv virt Gerd Hoffmann
2025-03-19 14:22 ` Daniel P. Berrangé
2025-03-19 15:04 ` Daniel Henrique Barboza
2025-03-19 14:11 ` [PATCH v3 5/6] hw/uefi-vars-sysbus: allow for loongarch virt Gerd Hoffmann
2025-03-19 14:22 ` Daniel P. Berrangé
2025-03-19 14:11 ` Gerd Hoffmann [this message]
2025-03-19 14:21 ` [PATCH v3 6/6] docs/firmware: add feature flag for host uefi variable store 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=20250319141159.1461621-7-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=berrange@redhat.com \
--cc=dbarboza@ventanamicro.com \
--cc=gaosong@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=kchamart@redhat.com \
--cc=liwei1518@gmail.com \
--cc=maobibo@loongson.cn \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).