From: Baolong Duan <blduan@linux.alibaba.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair23@gmail.com,
dbarboza@ventanamicro.com, cxx194832@alibaba-inc.com,
zengxiangyi.zxy@alibaba-inc.com,
Baolong Duan <blduan@linux.alibaba.com>
Subject: [RFC PATCH v1 13/17] accel/kvm: only register the DRAM slot of a CoVE guest
Date: Fri, 31 Jul 2026 11:50:07 +0800 [thread overview]
Message-ID: <20260731035011.4178103-14-blduan@linux.alibaba.com> (raw)
In-Reply-To: <20260731035011.4178103-1-blduan@linux.alibaba.com>
The TSM tracks the confidential region of a TEE VM itself. Registering
the remaining memory slots of the machine, such as the mask ROM or the
flash, overwrites that region and the guest fails to start.
Filtering them by slot number is a workaround rather than a solution:
the machine should describe which regions belong to the confidential
guest instead. Suggestions on how to express that are very welcome.
Signed-off-by: Baolong Duan <blduan@linux.alibaba.com>
---
accel/kvm/kvm-all.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index 005abb1c54..2753bf8b8b 100644
--- a/accel/kvm/kvm-all.c
+++ b/accel/kvm/kvm-all.c
@@ -26,6 +26,7 @@
#include "qapi/error.h"
#include "hw/pci/msi.h"
#include "hw/pci/msix.h"
+#include "hw/riscv/cove.h"
#include "hw/s390x/adapter.h"
#include "gdbstub/enums.h"
#include "system/kvm_int.h"
@@ -393,6 +394,16 @@ static int kvm_set_user_memory_region(KVMMemoryListener *kml, KVMSlot *slot, boo
struct kvm_userspace_memory_region2 mem = {};
int ret;
+ /*
+ * Only the DRAM slot is registered with KVM for a CoVE guest: the TSM
+ * tracks the confidential region of the TVM itself and registering the
+ * other slots (MROM, flash, ...) would overwrite it.
+ */
+ if (riscv_cove_vm_active() && (slot->slot & 0xffff) != 0 &&
+ slot->memory_size > 0) {
+ return 0;
+ }
+
mem.slot = slot->slot | (kml->as_id << 16);
mem.guest_phys_addr = slot->start_addr;
mem.userspace_addr = (unsigned long)slot->ram;
--
2.34.1
next prev parent reply other threads:[~2026-07-31 6:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 3:49 [RFC PATCH v1 00/17] target/riscv: Add KVM CoVE confidential VM support Baolong Duan
2026-07-31 3:49 ` [RFC PATCH v1 01/17] docs/system/riscv/virt: document the cove-vm machine option Baolong Duan
2026-07-31 3:49 ` [RFC PATCH v1 02/17] hw/riscv/virt: add the cove-vm machine property Baolong Duan
2026-07-31 3:49 ` [RFC PATCH v1 03/17] target/riscv/kvm: create and measure a CoVE TEE VM Baolong Duan
2026-07-31 3:49 ` [RFC PATCH v1 04/17] accel/kvm: add kvm_gpa_to_userspace_addr() Baolong Duan
2026-07-31 3:49 ` [RFC PATCH v1 05/17] hw/riscv/boot: load and measure the images of a CoVE guest Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 06/17] hw/riscv/virt: measure the device tree " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 07/17] hw/riscv: adapt " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 08/17] hw/riscv/virt: use MSIs only for " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 09/17] hw/intc/riscv_aplic: emulate the APLIC " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 10/17] target/riscv/kvm: skip unsupported KVM requests " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 11/17] hw/virtio: force modern virtio " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 12/17] hw/net/virtio-net: do not use vhost " Baolong Duan
2026-07-31 3:50 ` Baolong Duan [this message]
2026-07-31 3:50 ` [RFC PATCH v1 14/17] accel/kvm: skip MSI route updates " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 15/17] accel/kvm: pin the vCPU threads of " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 16/17] accel/kvm: terminate on a system event " Baolong Duan
2026-07-31 3:50 ` [RFC PATCH v1 17/17] hw/core/machine-qmp-cmds: shut down a CoVE guest on reset Baolong Duan
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=20260731035011.4178103-14-blduan@linux.alibaba.com \
--to=blduan@linux.alibaba.com \
--cc=alistair23@gmail.com \
--cc=cxx194832@alibaba-inc.com \
--cc=dbarboza@ventanamicro.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zengxiangyi.zxy@alibaba-inc.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 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.