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 4/6] hw/uefi-vars-sysbus: allow for riscv virt
Date: Wed, 19 Mar 2025 15:11:56 +0100 [thread overview]
Message-ID: <20250319141159.1461621-5-kraxel@redhat.com> (raw)
In-Reply-To: <20250319141159.1461621-1-kraxel@redhat.com>
Allow the device being added to riscv virt VMs.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/riscv/virt.c | 2 ++
hw/uefi/Kconfig | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
index dae46f4733cd..e517002fdfc7 100644
--- a/hw/riscv/virt.c
+++ b/hw/riscv/virt.c
@@ -57,6 +57,7 @@
#include "hw/acpi/aml-build.h"
#include "qapi/qapi-visit-common.h"
#include "hw/virtio/virtio-iommu.h"
+#include "hw/uefi/var-service-api.h"
/* KVM AIA only supports APLIC MSI. APLIC Wired is always emulated by QEMU. */
static bool virt_use_kvm_aia_aplic_imsic(RISCVVirtAIAType aia_type)
@@ -1935,6 +1936,7 @@ static void virt_machine_class_init(ObjectClass *oc, void *data)
hc->plug = virt_machine_device_plug_cb;
machine_class_allow_dynamic_sysbus_dev(mc, TYPE_RAMFB_DEVICE);
+ machine_class_allow_dynamic_sysbus_dev(mc, TYPE_UEFI_VARS_SYSBUS);
#ifdef CONFIG_TPM
machine_class_allow_dynamic_sysbus_dev(mc, TYPE_TPM_TIS_SYSBUS);
#endif
diff --git a/hw/uefi/Kconfig b/hw/uefi/Kconfig
index ca6c2bc46a96..f139008b632b 100644
--- a/hw/uefi/Kconfig
+++ b/hw/uefi/Kconfig
@@ -1,3 +1,3 @@
config UEFI_VARS
bool
- default y if X86_64 || AARCH64
+ default y if X86_64 || AARCH64 || RISCV64
--
2.48.1
next prev parent reply other threads:[~2025-03-19 14:13 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 ` Gerd Hoffmann [this message]
2025-03-19 14:22 ` [PATCH v3 4/6] hw/uefi-vars-sysbus: allow for riscv virt 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 ` [PATCH v3 6/6] docs/firmware: add feature flag for host uefi variable store Gerd Hoffmann
2025-03-19 14:21 ` 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-5-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).