Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	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,
	lorenzo.pieralisi@linaro.org, enju.kohei@fujitsu.com,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC v4 11/24] target/arm/kvm-rme: Populate Realm with runtime images
Date: Fri, 23 Oct 2026 08:58:38 +0200	[thread overview]
Message-ID: <atsFnklBAg73Smes@red-moon> (raw)
In-Reply-To: <ff029f82-07e2-469b-a758-6d27212a9227@redhat.com>

On Fri, Oct 23, 2026 at 09:30:36AM +1000, Gavin Shan wrote:
> On 10/23/26 12:34 AM, Lorenzo Pieralisi wrote:
> > On Wed, Oct 21, 2026 at 10:24:56PM +1000, Gavin Shan wrote:
> > > On 10/21/26 7:47 PM, Lorenzo Pieralisi wrote:
> > > > On Fri, Oct 02, 2026 at 01:45:40PM +1000, Gavin Shan wrote:
> > > > > On 9/4/26 5:35 AM, Mathieu Poirier wrote:
> > > > > > From: Jean-Philippe Brucker <jean-philippe@linaro.org>
> > > > > > 
> > > > > > Once the Realm descriptor has been created, tell KVM to transfer runtime
> > > > > > images (kernel, DT, and rootfs) from guest memory to Realm memory.
> > > > > > 
> > > > > > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> > > > > > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@linaro.org>
> > > > > > Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > > > > > ---
> > > > > >     target/arm/kvm-rme.c | 76 ++++++++++++++++++++++++++++++++++++++++++++
> > > > > >     1 file changed, 76 insertions(+)
> > > > > > 
> > > > > > diff --git a/target/arm/kvm-rme.c b/target/arm/kvm-rme.c
> > > > > > index 9985f5daba89..c082a5d8f3d1 100644
> > > > > > --- a/target/arm/kvm-rme.c
> > > > > > +++ b/target/arm/kvm-rme.c
> > > > > > @@ -15,6 +15,7 @@
> > > > > >     #include "migration/blocker.h"
> > > > > >     #include "qapi/error.h"
> > > > > >     #include "qemu/error-report.h"
> > > > > > +#include "qemu/memalign.h"
> > > > > >     #include "qom/object_interfaces.h"
> > > > > >     #include "system/confidential-guest-support.h"
> > > > > >     #include "system/kvm.h"
> > > > > > @@ -43,12 +44,87 @@ OBJECT_DEFINE_SIMPLE_TYPE_WITH_INTERFACES(RmeGuest, rme_guest, RME_GUEST,
> > > > > >     static RmeGuest *rme_guest;
> > > > > > +static int rme_populate_range(const RmeRamRegion *region, bool measure,
> > > > > > +                              Error **errp)
> > > > > > +{
> > > > > > +    int ret;
> > > > > > +    void *buffer;
> > > > > > +    hwaddr size = region->size;
> > > > > > +    hwaddr base = region->base;
> > > > > > +    hwaddr start = QEMU_ALIGN_DOWN(base, RME_PAGE_SIZE);
> > > > > > +    hwaddr end = QEMU_ALIGN_UP(base + size, RME_PAGE_SIZE);
> > > > > > +    struct kvm_arm_rmi_populate populate_args;
> > > > > > +    size_t aligned_size = ROUND_UP(region->size, qemu_real_host_page_size());
> > > > > 
> > > > > s/qemu_real_host_page_size()/RME_PAGE_SIZE
> > > > 
> > > > It will always have to be qemu_real_host_page_size(), KVM configures it
> > > > that way.
> > > > 
> > > > > > +
> > > > > > +    if (!region->data) {
> > > > > > +        return -ENODEV;
> > > > > > +    }
> > > > > > +
> > > > > > +    ret = kvm_set_memory_attributes_private(start, end - start);
> > > > > > +    if (ret) {
> > > > > > +        error_report("RME: failed to configure initial"
> > > > > > +                     "private guest memory");
> > > > > > +        return ret;
> > > > > > +    }
> > > > > > +
> > > > > > +    /* Allocate page-aligned memory */
> > > > > > +    buffer = qemu_memalign(qemu_real_host_page_size(), aligned_size);
> > > > > > +
> > > > > > +    if (!buffer) {
> > > > > > +        return -ENOMEM;
> > > > > > +    }
> > > > > > +
> > > > > > +    memset(buffer, 0, aligned_size);
> > > > > > +    memcpy(buffer, region->data, region->size);
> > > > > > +
> > > > > > +    populate_args = (struct kvm_arm_rmi_populate) {
> > > > > > +        .base = start,
> > > > > > +        .size = end - start,
> > > > > > +        .source_uaddr = (uintptr_t)buffer,
> > > > > > +        .flags = measure ? KVM_ARM_RMI_POPULATE_FLAGS_MEASURE : 0,
> > > > > > +    };
> > > > > > +
> > > > > > +    while (populate_args.size > 0) {
> > > > > > +        ret = kvm_vm_ioctl(kvm_state, KVM_ARM_RMI_POPULATE, &populate_args, 0);
> > > > > > +        if (ret) {
> > > > > > +            error_setg_errno(errp, -ret,
> > > > > > +                "failed to populate realm [0x%"HWADDR_PRIx", 0x%"HWADDR_PRIx")",
> > > > > > +                start, end);
> > > > > > +            break;
> > > > > > +        }
> > > > > > +    }
> > > > > > +
> > > > > > +    qemu_vfree(buffer);
> > > > > > +
> > > > > > +    return ret;
> > > > > > +}
> > > > > > +
> > > > > 
> > > > > I doubt that the unaligned regions (RmeRamRegion) are allowed. For example,
> > > > > the region [4KB 64KB+4KB] is turned to the aligned range [0 128KB] when RME_PAGE_SIZE
> > > > > is 64KB. The question is how do we know the added regions due to the alignment
> > > > > ([0 4KB] and [64KB+4KB 128KB]) are safe for kvm_vm_ioctl(KVM_ARM_RMI_POPULATE).
> > > > 
> > > > Getting back to this because it is important. Can you define "safe" here ?
> > > > 
> > > > I think it is VMM's role to load with the required alignment and make
> > > > sure it does not double populate (that is anyway prevented by KVM), what was
> > > > your concern here to make sure we are in agreement ?
> > > > 
> > > 
> > > For example, there are two regions are populated: [0 4KB] and [4KB 64KB] on a 64KB
> > > host. With the alignment considered, we're populating [0 64KB] for region [0 4KB],
> > > and [0 64KB] for [4KB 64KB]. [0 64KB] are populated for twice. Is this allowed by
> > > TF-RMM? If it's allowed by TF-RMM, the data populated in the first time is overwritten
> > > by the second population.
> > 
> > It is not allowed by the RMM and it is a VMM bug that we have to prevent.
> > 
> 
> Ok, thanks for your confirm. It's why I asked if we ever see an unaligned
> Rom region. If all Rom regions are aligned to host page size, then we needn't
> to handle the unaligned Rom regions in rme_populate_range(). Otherwise, we
> need come up with a solution to address the issue.
> 
> The solution would be to generate a temporary region list based on the existing
> Rom region list. For each region in the temporary list, its start/size are well
> aligned to host page size, and the temporary buffer is allocated, and the data
> is properly copied over from the original Rom region. The population is done
> based on the temporary list. For example, we need to have [0 64kb], [128kb 192kb]
> regions in the temporary list if we have Rom region [0 1kb], [4kb 5kb] [16kb 17kb],
> [132kb 133kb], [136kb 140kb]. The host page size is assumed to be 64kb in the example.
> 
>    [0 64kb] covers [0 1kb], [4kb 5kb] [16kb 17kb]
>    [128kb 192kb] covers [132kb 133kb], [136kb 140kb]

That's exactly what needs to be done.

Thanks,
Lorenzo

> Thanks,
> Gavin
> 
> > Thanks,
> > Lorenzo
> > 
> > > Thanks,
> > > Gavin
> > > 
> > > > Thanks,
> > > > Lorenzo
> > > > 
> > > > > I guess we probably just reject unaligned regions if they're not expected.
> > > > > 
> > > > > Even if the unaligned regions are allowed, they seem not well handled.
> > > > > 
> > > > > - @aligned_size is still 64KB instead of the 128KB ?
> > > > > - In "memcpy(buffer, region->data, region->size);", the blob data would be copied to
> > > > >     [4KB, 4KB+64KB]. However, we're copying the data to [0 64KB] now.
> > > > > 
> > > > > > +static void rme_populate_ram_region(gpointer data, gpointer err)
> > > > > > +{
> > > > > > +    Error **errp = err;
> > > > > > +    const RmeRamRegion *region = data;
> > > > > > +
> > > > > > +    if (*errp) {
> > > > > > +        return;
> > > > > > +    }
> > > > > > +
> > > > > > +    rme_populate_range(region, /* measure */ true, errp);
> > > > > > +}
> > > > > > +
> > > > > >     static void rme_vm_state_change(void *opaque, bool running, RunState state)
> > > > > >     {
> > > > > > +    Error *errp = NULL;
> > > > > > +
> > > > > >         if (!running) {
> > > > > >             return;
> > > > > >         }
> > > > > > +    g_slist_foreach(rme_guest->ram_regions, rme_populate_ram_region, &errp);
> > > > > > +    g_slist_free_full(g_steal_pointer(&rme_guest->ram_regions), g_free);
> > > > > > +    if (errp) {
> > > > > > +        return;
> > > > > > +    }
> > > > > > +
> > > > > >         kvm_mark_guest_state_protected();
> > > > > >     }
> > > > > 
> > > > > Thanks,
> > > > > Gavin
> > > > > 
> > > > 
> > > 
> > 
> 

  reply	other threads:[~2026-10-23  6:58 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 19:35 [RFC v4 00/24] Add Realm support to QEMU-VMM Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 01/24] linux-headers: Add RME related definitions Mathieu Poirier
2026-09-04  6:07   ` Gavin Shan
2026-09-04 16:24     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 02/24] target/arm/kvm: Return immediately on error in kvm_arch_init() Mathieu Poirier
2026-09-15 21:01   ` Michael Roth
2026-09-30 21:24     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 03/24] target/arm: Add confidential guest support Mathieu Poirier
2026-09-07  8:49   ` Markus Armbruster
2026-09-15 21:27   ` Michael Roth
2026-09-22  8:01     ` Lorenzo Pieralisi
2026-09-24  3:12       ` Kohei Enju
2026-09-30 21:28         ` Mathieu Poirier
2026-10-19 20:46         ` Mathieu Poirier
2026-10-20 11:02           ` Lorenzo Pieralisi
2026-10-20 17:27             ` Mathieu Poirier
2026-10-20 18:12               ` Michael Roth
2026-10-21 13:42           ` Gavin Shan
2026-09-03 19:35 ` [RFC v4 04/24] target/arm/kvm-rme: Add mechanic to initialize realms Mathieu Poirier
2026-10-01 23:42   ` Gavin Shan
2026-09-03 19:35 ` [RFC v4 05/24] target/arm/kvm: Split kvm_arch_get/put_registers Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 06/24] target/arm/kvm-rme: Initialize vCPU Mathieu Poirier
2026-10-02  0:53   ` Gavin Shan
2026-10-15 20:29     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 07/24] target/arm/kvm: Create scratch Realm VM when requested Mathieu Poirier
2026-09-04  3:09   ` Kohei Enju
2026-09-04 16:25     ` Mathieu Poirier
2026-10-02  1:05   ` Gavin Shan
2026-10-15 20:31     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 08/24] target/arm/kvm: Use kvm_vm_check_extension() where necessary Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 09/24] hw/core/loader: Add a ROM loader notifier Mathieu Poirier
2026-09-15 22:36   ` Michael Roth
2026-10-02  1:15   ` Gavin Shan
2026-10-15 20:31     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 10/24] target/arm/kvm-rme: Keep track of images loaded in Realm memory Mathieu Poirier
2026-09-15 22:50   ` Michael Roth
2026-09-16 21:40     ` Mathieu Poirier
2026-10-02  1:23   ` Gavin Shan
2026-10-16 17:14     ` Mathieu Poirier
2026-09-03 19:35 ` [RFC v4 11/24] target/arm/kvm-rme: Populate Realm with runtime images Mathieu Poirier
2026-10-02  3:45   ` Gavin Shan
2026-10-02  9:27     ` Lorenzo Pieralisi
2026-10-16 20:08     ` Mathieu Poirier
2026-10-17  1:06       ` Gavin Shan
2026-10-17  7:46         ` Lorenzo Pieralisi
2026-10-19 20:23         ` Mathieu Poirier
2026-10-21  9:47     ` Lorenzo Pieralisi
2026-10-21 12:24       ` Gavin Shan
2026-10-22 14:34         ` Lorenzo Pieralisi
2026-10-22 23:30           ` Gavin Shan
2026-10-23  6:58             ` Lorenzo Pieralisi [this message]
2026-09-03 19:35 ` [RFC v4 12/24] target/arm/cpu: Set number of breakpoints and watchpoints in KVM Mathieu Poirier
2026-10-02  4:06   ` Gavin Shan
2026-10-16 22:53     ` Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 13/24] target/arm/cpu: Set number of PMU counters " Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 14/24] target/arm/cpu: Don't read Realm registers Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 15/24] hw/arm/virt: Set proper conduit method for Realms Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 16/24] hw/arm/virt: Embed Realm VM type with IPA address space Mathieu Poirier
2026-10-02  4:16   ` Gavin Shan
2026-09-03 19:36 ` [RFC v4 17/24] hw/arm/virt: Reserve one bit of guest physical address for RME Mathieu Poirier
2026-10-02  4:19   ` Gavin Shan
2026-10-19 20:00     ` Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 18/24] hw/arm/virt: Disable DTB randomness for confidential VMs Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 19/24] hw/arm/virt: Move virt_flash_create() to machvirt_init() Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 20/24] hw/arm/virt: Use RAM instead of flash for confidential guest firmware Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 21/24] target/arm/kvm-rme: Add DMA remapping for the shared memory region Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 22/24] docs/interop/firmware.json: Add arm-rme firmware feature Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 23/24] hw/arm/boot: Load DTB as is for confidential VMs Mathieu Poirier
2026-09-03 19:36 ` [RFC v4 24/24] hw/arm/boot: Skip bootloader for confidential guests Mathieu Poirier
2026-09-21  4:05 ` [RFC v4 00/24] Add Realm support to QEMU-VMM Gavin Shan
2026-10-02 20:31   ` Mathieu Poirier
2026-10-21 21:03   ` 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=atsFnklBAg73Smes@red-moon \
    --to=lpieralisi@kernel.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=eblake@redhat.com \
    --cc=enju.kohei@fujitsu.com \
    --cc=gshan@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lorenzo.pieralisi@linaro.org \
    --cc=mathieu.poirier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox