From: Steven Price <steven.price@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
James Morse <james.morse@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Joey Gouly <joey.gouly@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Christoffer Dall <christoffer.dall@arm.com>,
Fuad Tabba <tabba@google.com>,
linux-coco@lists.linux.dev,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
Gavin Shan <gshan@redhat.com>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Alper Gun <alpergun@google.com>,
"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Emi Kisanuki <fj0570is@fujitsu.com>,
Vishal Annapurve <vannapurve@google.com>,
WeiLin.Chang@arm.com, Lorenzo Pieralisi <lpieralisi@kernel.org>,
Kohei Enju <enju.kohei@fujitsu.com>
Subject: Re: [PATCH v2 08/12] KVM: arm64: CCA: Add Realm RTT mapping and invalidation helpers
Date: Mon, 16 Nov 2026 11:30:11 +0000 [thread overview]
Message-ID: <9637055c-a948-4a7b-8e6f-dc8467da9a14@arm.com> (raw)
In-Reply-To: <9f45adbf-6f29-432f-9880-bfd585b7c0bb@arm.com>
On 13/11/2026 19:25, Suzuki K Poulose wrote:
> On 11/11/2026 14:57, Steven Price wrote:
>> Add the RMI RTT creation and unmap helpers needed by CCA Realm stage-2
>> memory operations. REC exit handling and guest requested RIPAS changes
>> follow in the vCPU series.
>>
>> Signed-off-by: Steven Price <steven.price@arm.com>
>>
>> ---
>> Changes since v1:
>> - Rework RTT creation and folding around missing or existing RTTs.
>> Use a shared RMI block-size helper and handle alignment, partial
>> progress and errors in range operations.
>> ---
>> arch/arm64/include/asm/kvm_rmi.h | 8 +
>> arch/arm64/kvm/rmi.c | 378 ++++++++++++++++++++++++++++++-
>> drivers/firmware/arm_rmm/rmi.c | 10 -
>> include/linux/arm-rmi-cmds.h | 8 +
>> 4 files changed, 385 insertions(+), 19 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/kvm_rmi.h b/arch/arm64/include/
>> asm/kvm_rmi.h
>> index 58d825e40bdf..e64c3bcce160 100644
>> --- a/arch/arm64/include/asm/kvm_rmi.h
>> +++ b/arch/arm64/include/asm/kvm_rmi.h
>> @@ -81,6 +81,14 @@ int kvm_init_realm(struct kvm *kvm);
>> void kvm_destroy_realm(struct kvm *kvm);
>> int kvm_realm_teardown_stage2(struct kvm *kvm);
>> +enum kvm_gfn_range_filter;
>> +
>> +void kvm_realm_unmap_range_filter(struct kvm *kvm,
>> + unsigned long ipa,
>> + unsigned long size,
>> + bool may_block,
>> + enum kvm_gfn_range_filter attr_filter);
>> +
>> static inline bool kvm_realm_is_private_address(struct realm *realm,
>> unsigned long addr)
>> {
>> diff --git a/arch/arm64/kvm/rmi.c b/arch/arm64/kvm/rmi.c
>> index b904e6541fb0..5aa34d68de59 100644
>> --- a/arch/arm64/kvm/rmi.c
>> +++ b/arch/arm64/kvm/rmi.c
>> @@ -11,14 +11,6 @@
>> #include <asm/kvm_pgtable.h>
>> #include <asm/virt.h>
>> -static inline unsigned long rmi_rtt_level_mapsize(int level)
>> -{
>> - if (WARN_ON(level > KVM_PGTABLE_LAST_LEVEL))
>> - return PAGE_SIZE;
>> -
>> - return (1UL << ARM64_HW_PGTABLE_LEVEL_SHIFT(level));
>> -}
>> -
>> u32 kvm_rmm_ipa_limit(void)
>> {
>> return u64_get_bits(rmi_feat_reg(0), RMI_FEATURE_REGISTER_0_S2SZ);
>> @@ -29,6 +21,75 @@ static int get_start_level(struct realm *realm)
>> return 4 - max(2, stage2_pgtable_levels(realm->ia_bits));
>> }
>> +static int find_map_level(struct realm *realm,
>> + unsigned long start,
>> + unsigned long end)
>> +{
>> + int level = KVM_PGTABLE_LAST_LEVEL;
>> +
>> + while (level > get_start_level(realm)) {
>
> minor nit: Could we save the start_level in a local variable. The
> generated assembly seems to be evaluating get_start_level() for each
> iteration. For that matter, I don't mind caching this in struct realm,
> as we end up calculating it quite often.
Hmm, I'm not sure why your compiler is calculting it once per loop - the
compiler should be able to see that get_start_level() is pure and
there's no write to realm. But pulling it out into a local variable
seems reasonable for clarity.
>> + unsigned long map_size = kvm_granule_size(level - 1);
>> +
>> + if (!IS_ALIGNED(start, map_size) ||
>> + (start + map_size) > end)
>> + break;
>> +
>> + level--;
>> + }
>> +
>> + return level;
>> +}
>> +
>> +static int undelegate_range_desc(unsigned long desc)
>> +{
>> + unsigned long size =
>> rmi_addr_block_size_to_bytes(RMI_ADDR_RANGE_BLOCK_SIZE(desc));
>> + unsigned long count = RMI_ADDR_RANGE_COUNT(desc);
>> + unsigned long addr = RMI_ADDR_RANGE_ADDR(desc);
>> + unsigned long state = RMI_ADDR_RANGE_STATE(desc);
>> +
>> + if (state == RMI_OP_MEM_UNDELEGATED)
>> + return 0;
>> +
>> + if (size * count == 0)
>> + return 0;
>> +
>> + return rmi_undelegate_range(addr, size * count);
>> +}
>> +
>> +static phys_addr_t alloc_delegated_granule(struct
>> kvm_mmu_memory_cache *mc)
>> +{
>> + phys_addr_t phys;
>> + void *virt;
>> +
>> + if (mc) {
>> + virt = kvm_mmu_memory_cache_alloc(mc);
>> + } else {
>> + virt = (void *)__get_free_page(GFP_ATOMIC | __GFP_ZERO |
>> + __GFP_ACCOUNT);
>> + }
>> +
>> + if (!virt)
>> + return PHYS_ADDR_MAX;
>> +
>> + phys = virt_to_phys(virt);
>> + if (rmi_delegate_page(phys)) {
>> + free_page((unsigned long)virt);
>> + return PHYS_ADDR_MAX;
>> + }
>> +
>> + return phys;
>> +}
>> +
>> +static phys_addr_t alloc_rtt(struct kvm_mmu_memory_cache *mc)
>> +{
>> + phys_addr_t phys = alloc_delegated_granule(mc);
>> +
>> + if (phys != PHYS_ADDR_MAX)
>> + kvm_account_pgtable_pages(phys_to_virt(phys), 1);
>> +
>> + return phys;
>> +}
>> +
>> static void free_rtt(phys_addr_t phys)
>> {
>> kvm_account_pgtable_pages(phys_to_virt(phys), -1);
>> @@ -36,6 +97,32 @@ static void free_rtt(phys_addr_t phys)
>> kvm_account_pgtable_pages(phys_to_virt(phys), 1);
>> }
>> +static long realm_rtt_create(struct realm *realm,
>> + unsigned long addr,
>> + int level,
>> + phys_addr_t phys)
>> +{
>> + addr = ALIGN_DOWN(addr, kvm_granule_size(level - 1));
>> + return rmi_rtt_create(virt_to_phys(realm->rd), phys, addr, level);
>> +}
>> +
>> +static long realm_rtt_fold(struct realm *realm,
>> + unsigned long addr,
>> + int level,
>> + phys_addr_t *rtt_granule)
>> +{
>> + unsigned long out_rtt;
>> + long ret;
>> +
>> + addr = ALIGN_DOWN(addr, kvm_granule_size(level - 1));
>> + ret = rmi_rtt_fold(virt_to_phys(realm->rd), addr, level, &out_rtt);
>> +
>> + if (ret == RMI_SUCCESS && rtt_granule)
>> + *rtt_granule = out_rtt;
>> +
>> + return ret;
>> +}
>> +
>> /*
>> * realm_rtt_destroy - Destroy an RTT at @level for @addr.
>> *
>> @@ -60,6 +147,47 @@ static long realm_rtt_destroy(struct realm *realm,
>> unsigned long addr,
>> return ret;
>> }
>> +static int realm_create_rtt_levels(struct realm *realm,
>> + unsigned long ipa,
>> + int level,
>> + int max_level,
>> + struct kvm_mmu_memory_cache *mc)
>> +{
>> + long ret = 0;
>> + phys_addr_t rtt = PHYS_ADDR_MAX;
>> +
>> + while (level++ < max_level) {
>> + if (rtt == PHYS_ADDR_MAX)
>> + rtt = alloc_rtt(mc);
>> + if (rtt == PHYS_ADDR_MAX)
>> + return -ENOMEM;
>> +
>> + ret = realm_rtt_create(realm, ipa, level, rtt);
>> + if (ret < 0)
>> + break;
>> +
>> + if (RMI_RESULT_STATUS(ret) == RMI_ERROR_RTT &&
>> + RMI_RESULT_DATA_LEVEL(ret) == level - 1) {
>> + /* The RTT already exists, reuse the granule at the next
>> level. */
>> + ret = 0;
>> + continue;
>> + }
>> +
>> + if (ret) {
>> + WARN(1, "Failed to create RTT at level %d: %ld\n",
>> + level, ret);
>> + ret = -ENXIO;
>> + break;
>> + }
>> + rtt = PHYS_ADDR_MAX;
>> + }
>> +
>> + if (rtt != PHYS_ADDR_MAX)
>> + free_rtt(rtt);
>> +
>> + return ret;
>> +}
>> +
>> static int realm_tear_down_rtt_level(struct realm *realm, int level,
>> unsigned long start, unsigned long end)
>> {
>> @@ -69,7 +197,9 @@ static int realm_tear_down_rtt_level(struct realm
>> *realm, int level,
>> if (WARN_ON(level > KVM_PGTABLE_LAST_LEVEL))
>> return -EINVAL;
>> - map_size = rmi_rtt_level_mapsize(level - 1);
>> + map_size = kvm_granule_size(level - 1);
>> + if (WARN_ON(!IS_ALIGNED(start, map_size)))
>> + return -EINVAL;
>>
>
> I see, as discussed please move it to the other patch.
Ack.
>> for (addr = start; addr < end; addr = next_addr) {
>> phys_addr_t rtt_granule;
>> @@ -156,12 +286,94 @@ static int realm_tear_down_rtt_range(struct
>> realm *realm,
>> start, end);
>> }
>> +/*
>> + * Returns 0 on successful fold, a negative value on error, a
>> positive value if
>> + * we were not able to fold all tables at this level.
>> + */
>> +static int realm_fold_rtt_level(struct realm *realm, int level,
>> + unsigned long start, unsigned long end)
>> +{
>> + int not_folded = 0;
>> + ssize_t map_size;
>> + unsigned long addr, next_addr;
>> +
>> + if (WARN_ON(level > KVM_PGTABLE_LAST_LEVEL))
>> + return -EINVAL;
>> +
>> + map_size = kvm_granule_size(level - 1);
>> +
>> + for (addr = start; addr < end; addr = next_addr) {
>> + phys_addr_t rtt_granule;
>> + long ret;
>> +
>> + next_addr = ALIGN(addr + 1, map_size);
>> +
>
> retry: // See below
>
>> + ret = realm_rtt_fold(realm, addr, level, &rtt_granule);
>> + if (ret < 0)
>> + return ret;
>> +
>> + switch (RMI_RESULT_STATUS(ret)) {
>> + case RMI_SUCCESS:
>> + free_rtt(rtt_granule);
>> + break;
>> + case RMI_ERROR_RTT: {
>> + int err_level = RMI_RESULT_DATA_LEVEL(ret);
>> +
>> + if (err_level < level) {
>> + /* No RTT at this level; skip the missing ancestor. */
>> + if (WARN_ON(err_level < get_start_level(realm)))
>> + return -EINVAL;
>> + next_addr = ALIGN(addr + 1,
>> + kvm_granule_size(err_level - 1));
>> + break;
>> + }
>> + if (level == KVM_PGTABLE_LAST_LEVEL) {
>> + not_folded++;
>> + break;
>> + }
>> + /* Recurse a level deeper */
>> + ret = realm_fold_rtt_level(realm,
>> + level + 1,
>> + addr,
>> + min(next_addr, end));
>> + if (ret < 0)
>> + return ret;
>> + if (ret) {
>> + not_folded++;
>> + break;
>> + }
>
> ---8>---
>
>> + /* Try once more after folding the child RTTs. */
>> + ret = realm_rtt_fold(realm, addr, level, &rtt_granule);
>> + if (ret < 0)
>> + return ret;
>> + if (RMI_RESULT_STATUS(ret) == RMI_SUCCESS) {
>> + free_rtt(rtt_granule);
>> + break;
>> + }
>> + if (RMI_RESULT_STATUS(ret) != RMI_ERROR_RTT) {
>> + WARN_ON(1);
>> + return -ENXIO;
>> + }
>
> ---<8---
>
> This seems like a repeat of the code above, could we do :
> goto retry;
I guess it depends on how much we "trust" the RMM/Linux not to be buggy.
The "repeat" is subtly different in that a second failure to fold
handles RMI_ERROR_RTT by continuing with the next entry rather than
retrying again. This prevents the code getting stuck in a loop if
recursing didn't help.
>> + not_folded++;
>> + break;
>> + }
>> + default:
>> + WARN_ON(1);
>> + return -ENXIO;
>> + }
>> + }
>> +
>> + return not_folded;
>> +}
>> +
>> static int realm_destroy_rtts(struct kvm *kvm)
>> {
>> struct realm *realm = &kvm->arch.realm;
>> unsigned int ia_bits = realm->ia_bits;
>> lockdep_assert_held(&kvm->arch.config_lock);
>> + if (WARN_ON_ONCE(!realm->stage2_unmapped))
>> + return -EINVAL;
>> return realm_tear_down_rtt_range(realm, 0, (1UL << ia_bits));
>> }
>> @@ -191,6 +403,154 @@ int kvm_realm_teardown_stage2(struct kvm *kvm)
>> return 0;
>> }
>> +static void realm_unmap_shared_range(struct kvm *kvm,
>> + unsigned long start,
>> + unsigned long end,
>> + bool may_block)
>> +{
>> + struct realm *realm = &kvm->arch.realm;
>> + unsigned long rd = virt_to_phys(realm->rd);
>> + unsigned long next_addr, addr;
>> + unsigned long shared_bit = BIT(realm->ia_bits - 1);
>> +
>> + if (start >= end)
>> + return;
>> +
>> + /*
>> + * Callers may pass either an IPA range or its shared alias. Add the
>> + * shared bit only for the former. Use addition so an exclusive
>> end at
>> + * shared_bit advances to the end of the IPA space.
>> + */
>> + if (start < shared_bit) {
>> + start += shared_bit;
>> + end += shared_bit;
>
> Could this overflow "end" to beyond ipa_size ? Why are we not using
>
> addr |= shared_bit;
>
> ?
The problem with doing an OR is in the case where we want to handle
until the end of the protected region, i.e.:
start = 0
end = shared_bit
That currently ends up with:
start = shared_bit;
end = shared_bit + shared_bit (or top of IPA).
I guess we could OR in the shared_bit every time we use "addr", but I
think this would make the loop below overly complex, especially since we
have "next_addr" coming back from the RMM.
Ultimately the callers already clamp "end" -
kvm_realm_unmap_range_filter() clamps it to shared_bit, and
realm_map_unprotected() passes a shared address in so doesn't hit this
addition case.
>> + }
>> +
>> + for (addr = start; addr < end; addr = next_addr) {
>> + long ret;
>> +
>> + ret = rmi_rtt_unprot_unmap(rd, addr, end, RMI_ADDR_TYPE_NONE,
>> + 0, &next_addr, NULL, NULL);
>
> I am wondering if this should be wrapped in a
>
> ret = rmi_rtt_unprot_unmap_single(rd, addr, end, &next_addr);
>
> But, we might replace these with an ADDR_TYPE_LIST in the near future,
> so may be not.
I have tried to keep the wrappers matching the RMM spec - as I find it
confusing matching up with the spec otherwise. So far I haven't actually
found a use for SMC_RMI_RTT_UNPROT_UNMAP returning the output addresses.
So logically we could remove those fields, but then it looks odd when
compared against the spec. Given this is (currently) the only call site
it seems unnecessary to have a wrapper.
>> + if (WARN_ON(ret < 0))
>> + return;
>> +
>> + switch (RMI_RESULT_STATUS(ret)) {
>> + case RMI_SUCCESS:
>> + break;
>> + case RMI_ERROR_RTT: {
>> + int err_level = RMI_RESULT_DATA_LEVEL(ret);
>> + int level = find_map_level(realm, addr, end);
>> +
>> + if (WARN_ON(err_level > KVM_PGTABLE_LAST_LEVEL))
>> + return;
>> +
>> + if (err_level >= level) {
>> + /* Nothing present, so skip */
>> + next_addr = ALIGN(addr + 1,
>> + kvm_granule_size(err_level));
>> + break;
>> + }
>> +
>> + ret = realm_create_rtt_levels(realm, addr, err_level,
>> + level, NULL);
>> + if (WARN_ON(ret))
>> + return;
>> + /* Retry with the RTT levels in place */
>> + next_addr = addr;
>> + break;
>> + }
>> + default:
>> + WARN_ON(1);
>> + return;
>> + }
>> +
>> + if (may_block)
>> + cond_resched_rwlock_write(&kvm->mmu_lock);
>> + }
>> +
>> + realm_fold_rtt_level(realm, get_start_level(realm) + 1,
>> + start, end);
>> +}
>> +
>> +static void realm_unmap_private_range(struct kvm *kvm,
>> + unsigned long start,
>> + unsigned long end,
>> + bool may_block)
>> +{
>> + struct realm *realm = &kvm->arch.realm;
>> + unsigned long rd = virt_to_phys(realm->rd);
>> + unsigned long next_addr, addr;
>> + long ret;
>> +
>> + for (addr = start; addr < end; addr = next_addr) {
>> + unsigned long out_range;
>> + unsigned long flags = RMI_ADDR_TYPE_SINGLE;
>> + /* TODO: Optimise using RMI_ADDR_TYPE_LIST */
>
> With RMI_ADDR_TYPE_LIST support, I think we may be able to merge
> realm_unmap_shared_range() with this, by simply selecting the call
> data_unmap vs unprot_unmap
Possibly. The two functions are quite similar, but there are a number of
difference in behaviour:
* Shared currently deals with the shared bit alias (as above), but
private doesn't.
* Private requires getting the physical addresses back and undelegating
them, shared doesn't.
* In my tree for v3 I've now got recovery for the case where memory
pressure prevents creating RTTs. For shared we can safely just unmap a
block, for private doing so will kill the VM (so I've got a KVM_BUG_ON()).
RMI_ADDR_TYPE_LIST will make the situation slightly more complex as the
private case will require walking that list - although we might be able
to hide all that in a helper function like undelegate_range_desc().
>> +
>> + ret = rmi_rtt_data_unmap(rd, addr, end, flags, 0,
>> + &next_addr, &out_range, NULL);
>> + if (WARN_ON(ret < 0))
>> + return;
>> +
>> + switch (RMI_RESULT_STATUS(ret)) {
>> + case RMI_SUCCESS:
>> + ret = undelegate_range_desc(out_range);
>> + if (WARN_ON(ret))
>> + return;
>> + break;
>> + case RMI_ERROR_RTT: {
>> + int err_level = RMI_RESULT_DATA_LEVEL(ret);
>> + int level = find_map_level(realm, addr, end);
>> +
>> + if (WARN_ON(err_level > KVM_PGTABLE_LAST_LEVEL))
>> + return;
>> +
>> + if (err_level >= level) {
>> + /* Nothing present, so skip this RTT entry. */
>> + next_addr = ALIGN(addr + 1,
>> + kvm_granule_size(err_level));
>> + break;
>> + }
>> +
>> + ret = realm_create_rtt_levels(realm, addr, err_level,
>> + level, NULL);
>> + if (WARN_ON(ret))
>> + return;
>> + /* Retry with the RTT levels in place. */
>> + next_addr = addr;
>> + break;
>> + }
>> + default:
>> + WARN_ON(1);
>> + return;
>> + }
>> +
>> + if (may_block)
>> + cond_resched_rwlock_write(&kvm->mmu_lock);
>> + }
>> +
>> + realm_fold_rtt_level(realm, get_start_level(realm) + 1,
>> + start, end);
>> +}
>> +
>> +void kvm_realm_unmap_range_filter(struct kvm *kvm, unsigned long start,
>> + unsigned long size, bool may_block,
>> + enum kvm_gfn_range_filter attr_filter)
>> +{
>> + unsigned long end = start + size;
>> + struct realm *realm = &kvm->arch.realm;
>> +
>> + if (!kvm_realm_is_created(kvm))
>> + return;
>> +
>
> Do we need to ensure we get the canonical GPA for start here ?
The below capping of "end" means that the GPA must be in the lower half
of the address range. Otherwise this effectively becomes a no-op. We
enforce that the memslots are in this lower half so we should always be
getting canonical GPAs here.
Thanks,
Steve
> Suzuki
>
>
>
>
>> + end = min(BIT(realm->ia_bits - 1), end);
>> +
>> + if (attr_filter & KVM_FILTER_SHARED)
>> + realm_unmap_shared_range(kvm, start, end, may_block);
>> + if (attr_filter & KVM_FILTER_PRIVATE)
>> + realm_unmap_private_range(kvm, start, end, may_block);
>> +}
>> +
>> void kvm_destroy_realm(struct kvm *kvm)
>> {
>> struct realm *realm = &kvm->arch.realm;
>> diff --git a/drivers/firmware/arm_rmm/rmi.c b/drivers/firmware/
>> arm_rmm/rmi.c
>> index 77255a90e0a6..a9f42c9a4f79 100644
>> --- a/drivers/firmware/arm_rmm/rmi.c
>> +++ b/drivers/firmware/arm_rmm/rmi.c
>> @@ -11,7 +11,6 @@
>> #include <linux/slab.h>
>> #include <asm/memory.h>
>> -#include <asm/pgtable-hwdef.h>
>> /* RMM v2.0 defines RmiFeatureRegister0 to RmiFeatureRegister4. */
>> static unsigned long rmi_feat_reg_cache[5] __ro_after_init;
>> @@ -183,15 +182,6 @@ int rmi_free_delegated_page(phys_addr_t phys)
>> }
>> EXPORT_SYMBOL_GPL(rmi_free_delegated_page);
>> -/*
>> - * Convert the RmiAddrBlockSize to actual size. This is used in
>> RmiDonateReq
>> - * and RmiAddrRangeDesc*.
>> - */
>> -static unsigned long rmi_addr_block_size_to_bytes(unsigned long
>> block_size_fld)
>> -{
>> - return BIT(ARM64_HW_PGTABLE_LEVEL_SHIFT(3 - block_size_fld));
>> -}
>> -
>> /*
>> * free_addr_range: Free memory described by the address range
>> entry, which may
>> * be partially consumed by RMM.
>> diff --git a/include/linux/arm-rmi-cmds.h b/include/linux/arm-rmi-cmds.h
>> index 6f43eac7c7be..71ba94eb72c0 100644
>> --- a/include/linux/arm-rmi-cmds.h
>> +++ b/include/linux/arm-rmi-cmds.h
>> @@ -13,8 +13,16 @@
>> #include <linux/string.h>
>> #include <linux/types.h>
>> +#include <asm/pgtable-hwdef.h>
>> +
>> #define RMI_MAX_ADDR_LIST 256
>> +/* Convert the block size used by RmiDonateReq and
>> RmiAddrRangeDesc. */
>> +static inline unsigned long rmi_addr_block_size_to_bytes(unsigned
>> long block_size)
>> +{
>> + return BIT(ARM64_HW_PGTABLE_LEVEL_SHIFT(3 - block_size));
>> +}
>> +
>
>
>> struct rmi_sro_state {
>> struct arm_smccc_1_2_regs regs;
>> int addr_count;
>
next prev parent reply other threads:[~2026-11-16 11:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 14:57 [PATCH v2 00/12] KVM: arm64: CCA: Prepare Realm memory management Steven Price
2026-11-11 14:57 ` [PATCH v2 01/12] KVM: arm64: CCA: Reserve the RMM mode Steven Price
2026-11-11 14:57 ` [PATCH v2 02/12] KVM: arm64: guest_memfd: Check mmap support when preparing memslot Steven Price
2026-11-11 15:21 ` Suzuki K Poulose
2026-11-12 10:43 ` Steven Price
2026-11-12 16:35 ` Suzuki K Poulose
2026-11-12 16:57 ` Suzuki K Poulose
2026-11-11 14:57 ` [PATCH v2 03/12] KVM: arm64: CCA: Introduce Realms Steven Price
2026-11-11 14:57 ` [PATCH v2 04/12] KVM: arm64: CCA: Check RMI support and features at init Steven Price
2026-11-12 16:39 ` Suzuki K Poulose
2026-11-13 11:49 ` Steven Price
2026-11-11 14:57 ` [PATCH v2 05/12] KVM: arm64: Handle attributes in stage2_unmap_range Steven Price
2026-11-11 14:57 ` [PATCH v2 06/12] KVM: arm64: CCA: Add basic infrastructure for creating a realm Steven Price
2026-11-11 14:57 ` [PATCH v2 07/12] KVM: arm64: CCA: Tear down RTTs Steven Price
2026-11-13 1:04 ` Suzuki K Poulose
2026-11-13 15:05 ` Steven Price
2026-11-13 16:26 ` Suzuki K Poulose
2026-11-13 16:40 ` Steven Price
2026-11-11 14:57 ` [PATCH v2 08/12] KVM: arm64: CCA: Add Realm RTT mapping and invalidation helpers Steven Price
2026-11-13 19:25 ` Suzuki K Poulose
2026-11-16 11:30 ` Steven Price [this message]
2026-11-11 14:57 ` [PATCH v2 09/12] KVM: Allow architectures to reject memslot changes before invalidation Steven Price
2026-11-11 14:57 ` [PATCH v2 10/12] KVM: arm64: CCA: Prevent memslot modifications after Realm creation Steven Price
2026-11-11 14:57 ` [PATCH v2 11/12] KVM: arm64: CCA: Support runtime faulting of memory Steven Price
2026-11-11 14:57 ` [PATCH v2 12/12] KVM: arm64: CCA: Add Realm stage-2 MMU operations Steven Price
2026-11-16 11:46 ` Suzuki K Poulose
2026-11-12 9:08 ` [PATCH v2 00/12] KVM: arm64: CCA: Prepare Realm memory management Kohei Enju
2026-11-12 9:41 ` Steven Price
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=9637055c-a948-4a7b-8e6f-dc8467da9a14@arm.com \
--to=steven.price@arm.com \
--cc=WeiLin.Chang@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=alpergun@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=enju.kohei@fujitsu.com \
--cc=fj0570is@fujitsu.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=sdonthineni@nvidia.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vannapurve@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®