From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Gavin Shan <gshan@redhat.com>
Cc: berrange@redhat.com, kchamart@redhat.com,
pierrick.bouvier@oss.qualcomm.com, peter.maydell@linaro.org,
mst@redhat.com, cohuck@redhat.com, pbonzini@redhat.com,
eblake@redhat.com, armbru@redhat.com, jpb@kernel.org,
lorenzo.pieralisi@linaro.org, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC v1 04/25] target/arm/kvm-rme: Add mechanic to initialize realms
Date: Mon, 13 Jul 2026 16:44:15 -0600 [thread overview]
Message-ID: <alVqP3H9N5Hh5jyF@p14s> (raw)
In-Reply-To: <618fa1ec-c986-4075-9b6f-c720b48d75ce@redhat.com>
On Mon, Jul 13, 2026 at 03:14:05PM +1000, Gavin Shan wrote:
> On 7/8/26 8:42 AM, Mathieu Poirier wrote:
> > From: Jean-Philippe Brucker <jean-philippe@linaro.org>
> >
> > Initialise an @rme_guest object and install a handler to get notified
> > when the Realm is ready to start. That way we can finish reading the
> > Realm once we know everything is in place.
> >
> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> > Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > ---
> > target/arm/kvm-rme.c | 50 +++++++++++++++++++++++++++++++++++++++++++
> > target/arm/kvm-stub.c | 5 +++++
> > target/arm/kvm.c | 7 +++++-
> > target/arm/kvm_arm.h | 9 ++++++++
> > 4 files changed, 70 insertions(+), 1 deletion(-)
> >
> > diff --git a/target/arm/kvm-rme.c b/target/arm/kvm-rme.c
> > index 42e1d1e7b859..b86b9d6a25cb 100644
> > --- a/target/arm/kvm-rme.c
> > +++ b/target/arm/kvm-rme.c
> > @@ -13,6 +13,7 @@
> > #include "kvm_arm.h"
> > #include "migration/blocker.h"
> > #include "qapi/error.h"
> > +#include "qemu/error-report.h"
> > #include "qom/object_interfaces.h"
> > #include "system/confidential-guest-support.h"
> > #include "system/kvm.h"
> > @@ -29,14 +30,63 @@ OBJECT_DEFINE_SIMPLE_TYPE_WITH_INTERFACES(RmeGuest, rme_guest, RME_GUEST,
> > CONFIDENTIAL_GUEST_SUPPORT,
> > { TYPE_USER_CREATABLE }, { })
> > +static RmeGuest *rme_guest;
> > +
> > +static void rme_vm_state_change(void *opaque, bool running, RunState state)
> > +{
> > + if (!running) {
> > + return;
> > + }
> > +
> > + kvm_mark_guest_state_protected();
> > +}
> > +
> > static void rme_guest_class_init(ObjectClass *oc, const void *data)
> > {
> > }
> > static void rme_guest_init(Object *obj)
> > {
> > + if (rme_guest) {
> > + error_report("a single instance of RmeGuest is supported");
> > + exit(1);
> > + }
> > + rme_guest = RME_GUEST(obj);
> > }
> > static void rme_guest_finalize(Object *obj)
> > {
> > }
> > +
> > +int kvm_arm_rme_init(MachineState *ms, KVMState *s)
> > +{
> > + static Error *rme_mig_blocker;
> > + ConfidentialGuestSupport *cgs = ms->cgs;
> > +
> > + if (!rme_guest) {
> > + return 0;
> > + }
> > +
> > + if (!cgs) {
> > + error_report("missing -machine confidential-guest-support parameter");
> > + return -EINVAL;
> > + }
> > +
> > + if (!kvm_vm_check_extension(s, KVM_CAP_ARM_RMI)) {
> > + error_report("KVM doesn't support Realms");
> > + return -ENODEV;
> > + }
> > +
> > + error_setg(&rme_mig_blocker, "RME: migration is not implemented");
> > + migrate_add_blocker(&rme_mig_blocker, &error_fatal);
> > +
> > + /*
> > + * The realm activation is done last, when the VM starts, after all images
> > + * have been loaded and all vcpus finalized.
> > + */
> > + qemu_add_vm_change_state_handler(rme_vm_state_change, NULL);
> > +
> > + cgs->require_guest_memfd = true;
> > + cgs->ready = true;
> > + return 0;
> > +}
>
> I think it's more reasonable to set ConfidentialGuestSupportClass::kvm_init to
> kvm_arm_rme_init in rme_guest_class_init(). confidential_guest_kvm_init()
> gets called in target/arm/kvm.c::kvm_arch_init(). With this, the pattern matches
> with that for x86.
I agree, it would be nice to align Arm with the other architectures that
support confidential guests. Let me see what I can do.
Thanks for the review, I'll look at your other comment tomorrow.
Mathieu
>
> More details can be found from commit 631a2ac5a4be ("i386/tdx: Implement tdx_kvm_init()
> to initialize TDX VM context").
>
> Thanks,
> Gavin
>
> > diff --git a/target/arm/kvm-stub.c b/target/arm/kvm-stub.c
> > index 88cbe8d85c41..eec1ca3dd2e5 100644
> > --- a/target/arm/kvm-stub.c
> > +++ b/target/arm/kvm-stub.c
> > @@ -119,3 +119,8 @@ char *kvm_print_register_name(uint64_t regidx)
> > {
> > g_assert_not_reached();
> > }
> > +
> > +int kvm_arm_rme_init(MachineState *ms, KVMState *s)
> > +{
> > + g_assert_not_reached();
> > +}
> > diff --git a/target/arm/kvm.c b/target/arm/kvm.c
> > index ed99be7fd80c..28d5643d6779 100644
> > --- a/target/arm/kvm.c
> > +++ b/target/arm/kvm.c
> > @@ -660,7 +660,12 @@ int kvm_arch_init(MachineState *ms, KVMState *s)
> > hw_breakpoints = g_array_sized_new(true, true,
> > sizeof(HWBreakpoint), max_hw_bps);
> > - return 0;
> > + ret = kvm_arm_rme_init(ms, s);
> > + if (ret) {
> > + error_report("Failed to enable RME: %s", strerror(-ret));
> > + }
> > +
> > + return ret;
> > }
> > unsigned long kvm_arch_vcpu_id(CPUState *cpu)
> > diff --git a/target/arm/kvm_arm.h b/target/arm/kvm_arm.h
> > index e7c40fb003e4..6d058b0e08a2 100644
> > --- a/target/arm/kvm_arm.h
> > +++ b/target/arm/kvm_arm.h
> > @@ -240,4 +240,13 @@ void arm_gic_cap_kvm_probe(GICCapability *v2, GICCapability *v3);
> > */
> > char *kvm_print_register_name(uint64_t regidx);
> > +/**
> > + * kvm_arm_rme_init
> > + * @ms: the machine state
> > + * @s: State of KVM
> > + *
> > + * Prepare the machine to be a Realm, if the user enabled it.
> > + */
> > +int kvm_arm_rme_init(MachineState *ms, KVMState *s);
> > +
> > #endif
>
next prev parent reply other threads:[~2026-07-13 22:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 22:42 [RFC v1 00/25] Add Realm support to QEMU-VMM Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 01/25] linux-headers: Add RME related definitions Mathieu Poirier
2026-07-10 1:09 ` Gavin Shan
2026-07-10 7:36 ` Lorenzo Pieralisi
2026-07-10 10:46 ` Lorenzo Pieralisi
2026-07-13 0:41 ` Gavin Shan
2026-07-13 21:11 ` Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 02/25] target/arm/kvm: Return immediately on error in kvm_arch_init() Mathieu Poirier
2026-07-08 5:08 ` Philippe Mathieu-Daudé
2026-07-07 22:42 ` [RFC v1 03/25] target/arm: Add confidential guest support Mathieu Poirier
2026-07-08 4:39 ` Markus Armbruster
2026-07-09 20:22 ` Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 04/25] target/arm/kvm-rme: Add mechanic to initialize realms Mathieu Poirier
2026-07-13 5:14 ` Gavin Shan
2026-07-13 22:44 ` Mathieu Poirier [this message]
2026-07-13 5:34 ` Gavin Shan
2026-07-07 22:42 ` [RFC v1 05/25] target/arm/kvm: Split kvm_arch_get/put_registers Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 06/25] target/arm/kvm-rme: Initialize vCPU Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 07/25] target/arm/kvm: Create scratch Realm VM when requested Mathieu Poirier
2026-07-13 5:30 ` Gavin Shan
2026-07-07 22:42 ` [RFC v1 08/25] target/arm/kvm: Use kvm_vm_check_extension() where necessary Mathieu Poirier
2026-07-13 0:43 ` Gavin Shan
2026-07-07 22:42 ` [RFC v1 09/25] target/arm/kvm-rme: Initialise Realm Initial Address space Mathieu Poirier
2026-07-09 23:44 ` Gavin Shan
2026-07-10 7:37 ` Lorenzo Pieralisi
2026-07-07 22:42 ` [RFC v1 10/25] hw/core/loader: Add a ROM loader notifier Mathieu Poirier
2026-07-14 10:52 ` Gavin Shan
2026-07-07 22:42 ` [RFC v1 11/25] target/arm/kvm-rme: Keep track of images loaded in Realm memory Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 12/25] target/arm/kvm-rme: Populate Realm with runtime images Mathieu Poirier
2026-07-14 10:56 ` Gavin Shan
2026-07-07 22:42 ` [RFC v1 13/25] target/arm/cpu: Set number of breakpoints and watchpoints in KVM Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 14/25] target/arm/cpu: Set number of PMU counters " Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 15/25] target/arm/cpu: Don't read Realm registers Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 16/25] hw/arm/virt: Set proper conduit method for Realms Mathieu Poirier
2026-07-08 5:12 ` Philippe Mathieu-Daudé
2026-07-07 22:42 ` [RFC v1 17/25] hw/arm/virt: Embed Realm VM type with IPA address space Mathieu Poirier
2026-07-07 22:42 ` [RFC v1 18/25] hw/arm/virt: Reserve one bit of guest physical address for RME Mathieu Poirier
2026-07-07 22:43 ` [RFC v1 19/25] hw/arm/virt: Disable DTB randomness for confidential VMs Mathieu Poirier
2026-07-07 22:43 ` [RFC v1 20/25] hw/arm/virt: Move virt_flash_create() to machvirt_init() Mathieu Poirier
2026-07-08 5:14 ` Philippe Mathieu-Daudé
2026-07-07 22:43 ` [RFC v1 21/25] hw/arm/virt: Use RAM instead of flash for confidential guest firmware Mathieu Poirier
2026-07-07 22:43 ` [RFC v1 22/25] target/arm/kvm-rme: Add DMA remapping for the shared memory region Mathieu Poirier
2026-07-07 22:43 ` [RFC v1 23/25] docs/interop/firmware.json: Add arm-rme firmware feature Mathieu Poirier
2026-07-08 4:37 ` Markus Armbruster
2026-07-08 5:16 ` Philippe Mathieu-Daudé
2026-07-07 22:43 ` [RFC v1 24/25] hw/arm/boot: Load DTB as is for confidential VMs Mathieu Poirier
2026-07-07 22:43 ` [RFC v1 25/25] hw/arm/boot: Skip bootloader for confidential guests Mathieu Poirier
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=alVqP3H9N5Hh5jyF@p14s \
--to=mathieu.poirier@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=gshan@redhat.com \
--cc=jpb@kernel.org \
--cc=kchamart@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lorenzo.pieralisi@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-arm@nongnu.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.