Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Steven Price <steven.price@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>,
	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>
Subject: Re: [PATCH v16 14/45] KVM: arm64: CCA: Add basic infrastructure for creating a realm
Date: Thu, 3 Sep 2026 14:20:01 +1000	[thread overview]
Message-ID: <551014ec-eafc-4a63-92f1-6efcf1ca4db1@redhat.com> (raw)
In-Reply-To: <56aa7422-ded5-449c-ba62-e7e56d229587@arm.com>

On 9/3/26 1:11 AM, Suzuki K Poulose wrote:
> On 01/09/2026 05:07, Gavin Shan wrote:
>> Hi Steve,
>>
>> On 8/3/26 11:43 PM, Steven Price wrote:
>>> Introduce the skeleton functions for creating and destroying a realm.
>>> The IPA size requested is checked against what the RMM supports.
>>>
>>> The actual work of constructing the realm will be added in future
>>> patches.
>>>
>>> Signed-off-by: Steven Price <steven.price@arm.com>
>>> ---
>>> Changes since v15:
>>>   * Remove realm->params and only temporarily allocate the page when the
>>>     realm is being created.
>>
>> [...]
>>
>>> ---
>>>   arch/arm64/include/asm/kvm_emulate.h | 24 +++++++++++
>>>   arch/arm64/include/asm/kvm_rmi.h     | 63 ++++++++++++++++++++++++++++
>>>   arch/arm64/kvm/arm.c                 | 12 ++++++
>>>   arch/arm64/kvm/mmu.c                 | 18 +++++++-
>>>   arch/arm64/kvm/rmi.c                 | 56 +++++++++++++++++++++++++
>>>   5 files changed, 171 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/arm64/include/asm/kvm_emulate.h b/arch/arm64/ include/asm/kvm_emulate.h
>>> index 5bf3d7e1d92c..e26d6755279f 100644
>>> --- a/arch/arm64/include/asm/kvm_emulate.h
>>> +++ b/arch/arm64/include/asm/kvm_emulate.h
>>> @@ -688,4 +688,28 @@ static inline void vcpu_set_hcrx(struct kvm_vcpu *vcpu)
>>>               vcpu->arch.hcrx_el2 |= HCRX_EL2_EnASR;
>>>       }
>>>   }
>>> +
>>> +static inline bool kvm_is_realm(struct kvm *kvm)
>>> +{
>>> +    if (static_branch_unlikely(&kvm_rmi_is_available))
>>> +        return kvm->arch.is_realm;
>>> +    return false;
>>> +}
>>> +
>>> +static inline enum realm_state kvm_realm_state(struct kvm *kvm)
>>> +{
>>> +    return READ_ONCE(kvm->arch.realm.state);
>>> +}
>>> +
>>> +static inline void kvm_set_realm_state(struct kvm *kvm,
>>> +                       enum realm_state new_state)
>>> +{
>>> +    WRITE_ONCE(kvm->arch.realm.state, new_state);
>>> +}
>>> +
>>> +static inline bool kvm_realm_is_created(struct kvm *kvm)
>>> +{
>>> +    return kvm_is_realm(kvm) && kvm_realm_state(kvm) != REALM_STATE_NONE;
>>> +}
>>> +
>>>   #endif /* __ARM64_KVM_EMULATE_H__ */
>>> diff --git a/arch/arm64/include/asm/kvm_rmi.h b/arch/arm64/include/ asm/kvm_rmi.h
>>> index 57d24b244c95..cefd00b76806 100644
>>> --- a/arch/arm64/include/asm/kvm_rmi.h
>>> +++ b/arch/arm64/include/asm/kvm_rmi.h
>>> @@ -6,12 +6,75 @@
>>>   #ifndef __ASM_KVM_RMI_H
>>>   #define __ASM_KVM_RMI_H
>>> +#include <linux/arm-smccc-rmi.h>
>>> +
>>> +/**
>>> + * enum realm_state - State of a Realm
>>> + *
>>> + * Mirrors the RMM's Realm lifecycle states where they are meaningful to KVM,
>>> + * with REALM_STATE_DYING being a KVM-internal state used to prevent further
>>> + * requests while teardown is in progress. KVM does not track REALM_SYSTEM_OFF
>>> + * or REALM_ZOMBIE separately as they naturally lead to teardown.
>>> + */
>>> +enum realm_state {
>>> +    /**
>>> +     * @REALM_STATE_NONE:
>>> +     *      Realm has not yet been created. rmi_realm_create() has not
>>> +     *      yet been called.
>>> +     */
>>> +    REALM_STATE_NONE,
>>> +    /**
>>> +     * @REALM_STATE_NEW:
>>> +     *      Realm is under construction, rmi_realm_create() has been
>>> +     *      called, but it is not yet activated. Pages may be populated.
>>> +     */
>>> +    REALM_STATE_NEW,
>>> +    /**
>>> +     * @REALM_STATE_ACTIVE:
>>> +     *      Realm has been created and is eligible for execution with
>>> +     *      rmi_rec_enter(). Pages may no longer be populated with
>>> +     *      rmi_data_create().
>>> +     */
>>> +    REALM_STATE_ACTIVE,
>>> +    /**
>>> +     * @REALM_STATE_DYING:
>>> +     *      Realm is in the process of being destroyed or has already been
>>> +     *      destroyed.
>>> +     */
>>> +    REALM_STATE_DYING,
>>> +    /**
>>> +     * @REALM_STATE_DEAD:
>>> +     *      Realm has been destroyed.
>>> +     */
>>> +    REALM_STATE_DEAD
>>> +};
>>> +
>>>   /**
>>>    * struct realm - Additional per VM data for a Realm
>>> + *
>>> + * @rd: Kernel mapping of the RMM-managed Realm Descriptor (RD) granule
>>> + * @sro: Preallocated SRO state context for Realm MMU operations
>>> + * @state: The lifetime state machine for the realm
>>> + * @ia_bits: Number of valid Input Address bits in the IPA
>>>    */
>>>   struct realm {
>>> +    void *rd;
>>> +    /*
>>> +     * Reused by RTT map/unmap SRO commands. Those commands are only
>>> +     * issued from Realm stage-2 map/unmap paths while kvm->mmu_lock is
>>> +     * held for write, including Realm fault handling where
>>> +     * kvm_fault_lock() takes the write side, so concurrent use is
>>> +     * serialized.
>>> +     */
>>> +    struct rmi_sro_state *sro;
>>> +    enum realm_state state;
>>> +    unsigned int ia_bits;
>>>   };
>>>   void kvm_init_rmi(void);
>>> +u32 kvm_rmm_ipa_limit(void);
>>> +
>>> +int kvm_init_realm(struct kvm *kvm);
>>> +void kvm_destroy_realm(struct kvm *kvm);
>>>   #endif /* __ASM_KVM_RMI_H */
>>> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
>>> index b961c22fce3d..c4d906861736 100644
>>> --- a/arch/arm64/kvm/arm.c
>>> +++ b/arch/arm64/kvm/arm.c
>>> @@ -266,6 +266,13 @@ int kvm_arch_init_vm(struct kvm *kvm, unsigned long type)
>>>       bitmap_zero(kvm->arch.vcpu_features, KVM_VCPU_MAX_FEATURES);
>>> +    /* Initialise the realm bits after the generic bits are enabled */
>>> +    if (kvm_is_realm(kvm)) {
>>> +        ret = kvm_init_realm(kvm);
>>> +        if (ret)
>>> +            goto err_uninit_mmu;
>>> +    }
>>> +
>>>       return 0;
>>>   err_uninit_mmu:
>>> @@ -328,6 +335,8 @@ void kvm_arch_destroy_vm(struct kvm *kvm)
>>>       kvm_unshare_hyp(kvm, kvm + 1);
>>>       kvm_arm_teardown_hypercalls(kvm);
>>> +    if (kvm_is_realm(kvm))
>>> +        kvm_destroy_realm(kvm);
>>>   }
>>>   static bool kvm_has_full_ptr_auth(void)
>>> @@ -488,6 +497,9 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
>>>           else
>>>               r = kvm_supports_cacheable_pfnmap();
>>>           break;
>>> +    case KVM_CAP_ARM_RMI:
>>> +        r = static_key_enabled(&kvm_rmi_is_available);
>>> +        break;
>>>       default:
>>>           r = 0;
>>> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
>>> index 6c941aaa10c6..8b9efa8a3539 100644
>>> --- a/arch/arm64/kvm/mmu.c
>>> +++ b/arch/arm64/kvm/mmu.c
>>> @@ -904,10 +904,14 @@ static struct kvm_pgtable_mm_ops kvm_s2_mm_ops = {
>>>   static int kvm_init_ipa_range(struct kvm_s2_mmu *mmu, unsigned long type)
>>>   {
>>> +    struct kvm *kvm = kvm_s2_mmu_to_kvm(mmu);
>>>       u32 kvm_ipa_limit = get_kvm_ipa_limit();
>>>       u64 mmfr0, mmfr1;
>>>       u32 phys_shift;
>>> +    if (kvm_is_realm(kvm))
>>> +        kvm_ipa_limit = kvm_rmm_ipa_limit();
>>> +
>>>       phys_shift = KVM_VM_TYPE_ARM_IPA_SIZE(type);
>>>       if (is_protected_kvm_enabled()) {
>>>           phys_shift = kvm_ipa_limit;
>>
>> get_kvm_ipa_limit() and variable 'kvm_ipa_limit' have been exposed through
>> KVM_CAP_ARM_VM_IPA_SIZE for both normal and realm VMs in this series. However,
>> the IPA limit determined by the feature-register-0 in TF-RMM, which is returned
>> by kvm_rmm_ipa_limit(), can be different from 'kvm_ipa_limit'.
>>
>> This brings confusion to VMM like qemu, where the request to create a realm VM is
>> rejected if the requested IPA size exceeds the limit, exposed by the host through
>> KVM_CAP_ARM_VM_IPA_SIZE. So the host needs to return correct IPA limit through
>> KVM_CAP_ARM_VM_IPA_SIZE for realm VM somewhere in this series?
> 
> You're right that the limit exposed by the KVM_CAP_ARM_VM_IPA_SIZE
> doesn't tell the VMM about the limit imposed by the RMM. The only way
> to expose this is via an ioctl() on the KVM VM fd. But the VM fd is
> created with an argument (type), which on arm64 unfortunately specifies
> the IPA Size. So, this is kind of a chicken and egg problem. Or the
> VMM can create a dummy Realm VM (with default IPA size of 0) and then
> run the cap.
> 
> On the other hand, given the Realm creation is measured, if the Realm
> can't be created with the "IPA Size" requested by the user, then there
> is no point in creating the Realm VM.
> 
> So, we decided that this failure condition was alright.
> 
> This was mentioned in one of the versions of the series, but got lost
> in the revisions.
> 
> If there is interest in getting this exposed, we could do something
> like the above. Or, the other option is limit the IPA size of the VM
> that can be created to RMM IPA limit, when we explicitly choose the
> KVM mode to be CCA (this is something that is coming in the next
> version)
> 

I was even wandering if KVM_CAP_ARM_RMI can be extended to return the limit.
For example, KVM_CAP_ARM_RMI is renamed to KVM_CAP_ARM_REALM_IPA_SIZE. 0 is
returned if Realm VM isn't supported. Otherwise, the IPA size enforced by
TF-RMM through the feature-register-0 is returned.

With above extension, the existing KVM_CAP_ARM_VM_IPA_SIZE is dedicated to
query the IPA size for the regular (or normal) VM, while KVM_CAP_ARM_REALM_IPA_SIZE
is used to get the IPA size for the Realm VM. VMM needs to decide which one
is to be used.

Another option could be splitting @arg in kvm_vm_ioctl_check_extension() into
two parts: (a) Indicator of the scope; (b) Specific capability. For (a), it
could be categorized into: (1) 0, global and not specific to any types of VMs;
(2) 1, indicating the capability is associated with a regular (normal) VM; (3)
2, indicating the capability is associated with a Realm VM. With this extension,
VMM uses ioctl(kvm_fd, KVM_CHECK_EXTENSION, (2UL << 48) | KVM_CAP_ARM_VM_IPA_SIZE)
to retrieve the IPA size of Realm VM that is enforced by TF-RMM. Besides, I'm not
sure if pKVM can be benefited from this splitting in long term.

Thanks,
Gavin
>>> @@ -957,9 +961,18 @@ static void stage2_destroy_range(struct kvm_pgtable *pgt, phys_addr_t addr,
>>>   static void kvm_stage2_destroy(struct kvm_pgtable *pgt)
>>>   {
>>> +    struct kvm *kvm = kvm_s2_mmu_to_kvm(pgt->mmu);
>>>       unsigned int ia_bits = VTCR_EL2_IPA(pgt->mmu->vtcr);
>>> -    stage2_destroy_range(pgt, 0, BIT(ia_bits));
>>> +    /*
>>> +     * Realm RTTs are inaccessible to the host and may contain stale data
>>> +     * after the RMM has released them. The non-root RTTs are explicitly
>>> +     * destroyed through RMI before the RD is destroyed; only the root PGD
>>> +     * pages remain to be freed here.
>>> +     */
>>> +    if (!kvm_is_realm(kvm))
>>> +        stage2_destroy_range(pgt, 0, BIT(ia_bits));
>>> +
>>>       KVM_PGT_FN(kvm_pgtable_stage2_destroy_pgd)(pgt);
>>>   }
>>> @@ -1001,6 +1014,8 @@ int kvm_init_stage2_mmu(struct kvm *kvm, struct kvm_s2_mmu *mmu, unsigned long t
>>>           return -EINVAL;
>>>       }
>>> +    mmu->arch = &kvm->arch;
>>> +
>>>       err = kvm_init_ipa_range(mmu, type);
>>>       if (err)
>>>           return err;
>>> @@ -1009,7 +1024,6 @@ int kvm_init_stage2_mmu(struct kvm *kvm, struct kvm_s2_mmu *mmu, unsigned long t
>>>       if (!pgt)
>>>           return -ENOMEM;
>>> -    mmu->arch = &kvm->arch;
>>>       err = KVM_PGT_FN(kvm_pgtable_stage2_init)(pgt, mmu, &kvm_s2_mm_ops);
>>>       if (err)
>>>           goto out_free_pgtable;
>>> diff --git a/arch/arm64/kvm/rmi.c b/arch/arm64/kvm/rmi.c
>>> index 247c4f033945..528b01d5d71d 100644
>>> --- a/arch/arm64/kvm/rmi.c
>>> +++ b/arch/arm64/kvm/rmi.c
>>> @@ -5,6 +5,8 @@
>>>   #include <linux/kvm_host.h>
>>> +#include <asm/kvm_emulate.h>
>>> +#include <asm/kvm_mmu.h>
>>>   #include <asm/kvm_pgtable.h>
>>>   #include <asm/rmi_cmds.h>
>>>   #include <asm/virt.h>
>>> @@ -14,6 +16,60 @@ static bool rmi_has_feature(int reg, unsigned long feature)
>>>       return !!u64_get_bits(rmi_feat_reg(reg), feature);
>>>   }
>>> +u32 kvm_rmm_ipa_limit(void)
>>> +{
>>> +    return u64_get_bits(rmi_feat_reg(0), RMI_FEATURE_REGISTER_0_S2SZ);
>>> +}
>>> +
>>> +void kvm_destroy_realm(struct kvm *kvm)
>>> +{
>>> +    struct realm *realm = &kvm->arch.realm;
>>> +    size_t pgd_size = kvm_pgtable_stage2_pgd_size(kvm->arch.mmu.vtcr);
>>> +
>>> +    if (!kvm_realm_is_created(kvm)) {
>>> +        kfree(realm->sro);
>>> +        realm->sro = NULL;
>>> +        return;
>>> +    }
>>> +
>>> +    kvm_set_realm_state(kvm, REALM_STATE_DYING);
>>> +
>>> +    if (realm->rd) {
>>> +        phys_addr_t rd_phys = virt_to_phys(realm->rd);
>>> +
>>> +        if (WARN_ON(rmi_realm_terminate(rd_phys, realm->sro)))
>>> +            return;
>>> +
>>> +        if (WARN_ON(rmi_realm_destroy(rd_phys, realm->sro)))
>>> +            return;
>>> +        free_delegated_page(rd_phys);
>>> +        realm->rd = NULL;
>>> +    }
>>> +
>>> +    if (WARN_ON(rmi_undelegate_range(kvm->arch.mmu.pgd_phys,
>>> +                     pgd_size)))
>>> +        return;
>>> +
>>> +    kvm_set_realm_state(kvm, REALM_STATE_DEAD);
>>> +
>>> +    /* Now that the realm is destroyed, free the entry-level RTTs. */
>>> +    kvm_free_stage2_pgd(&kvm->arch.mmu);
>>> +
>>> +    kfree(realm->sro);
>>> +    realm->sro = NULL;
>>> +}
>>> +
>>> +int kvm_init_realm(struct kvm *kvm)
>>> +{
>>> +    struct realm *realm = &kvm->arch.realm;
>>> +
>>> +    realm->sro = kmalloc_obj(*realm->sro);
>>> +    if (!realm->sro)
>>> +        return -ENOMEM;
>>> +
>>> +    return 0;
>>> +}
>>> +
>>>   static int rmm_check_features(void)
>>>   {
>>>       if (kvm_lpa2_is_enabled() &&
>>
> 



  reply	other threads:[~2026-09-03  4:20 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 13:43 [PATCH v16 00/45] arm64: Support for Arm CCA in KVM Steven Price
2026-08-03 13:43 ` [PATCH v16 01/45] firmware: arm_rmm: Add SMC definitions for calling the RMM Steven Price
2026-08-03 13:43 ` [PATCH v16 02/45] firmware: arm_rmm: Add wrappers for direct RMI calls Steven Price
2026-08-03 13:43 ` [PATCH v16 03/45] firmware: arm_rmm: Check for RMI support at init Steven Price
2026-08-03 13:43 ` [PATCH v16 04/45] firmware: arm_rmm: Configure the RMM with the host's page size Steven Price
2026-08-03 13:43 ` [PATCH v16 05/45] firmware: arm_rmm: Add support for SRO Steven Price
2026-08-03 13:43 ` [PATCH v16 06/45] firmware: arm_rmm: Ensure the RMM has GPT entries for memory Steven Price
2026-08-09  6:42   ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 07/45] arm64: mm: Handle Granule Protection Faults (GPFs) Steven Price
2026-08-11 14:44   ` Catalin Marinas
2026-08-11 15:11     ` Suzuki K Poulose
2026-08-12 12:42       ` Pavan Kondeti
2026-08-12 13:51         ` Catalin Marinas
2026-08-13 10:11           ` Will Deacon
2026-08-13 14:10             ` Pavan Kondeti
2026-08-13 15:28               ` Will Deacon
2026-08-14  8:45                 ` Pavan Kondeti
2026-08-14  9:20                   ` Will Deacon
2026-08-03 13:43 ` [PATCH v16 08/45] KVM: arm64: Include kvm_emulate.h in kvm/arm_psci.h Steven Price
2026-08-03 13:43 ` [PATCH v16 09/45] KVM: arm64: Avoid including linux/kvm_host.h in kvm_pgtable.h Steven Price
2026-08-03 13:43 ` [PATCH v16 10/45] KVM: arm64: CCA: Add wrappers for realm related RMIs Steven Price
2026-08-03 13:43 ` [PATCH v16 11/45] KVM: arm64: CCA: Check for RMI support at KVM init Steven Price
2026-08-04 14:55   ` Fuad Tabba
2026-08-04 14:59     ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 12/45] KVM: arm64: CCA: Check for LPA2 support Steven Price
2026-08-03 13:43 ` [PATCH v16 13/45] KVM: arm64: CCA: Define the user ABI Steven Price
2026-08-03 13:43 ` [PATCH v16 14/45] KVM: arm64: CCA: Add basic infrastructure for creating a realm Steven Price
2026-09-01  4:07   ` Gavin Shan
2026-09-02 15:11     ` Suzuki K Poulose
2026-09-03  4:20       ` Gavin Shan [this message]
2026-08-03 13:43 ` [PATCH v16 15/45] KVM: arm64: CCA: Don't expose unsupported capabilities for realm guests Steven Price
2026-09-01  4:29   ` Gavin Shan
2026-08-03 13:43 ` [PATCH v16 16/45] KVM: arm64: CCA: Allow passing the machine type in KVM creation Steven Price
2026-09-01  4:45   ` Gavin Shan
2026-08-03 13:43 ` [PATCH v16 17/45] KVM: arm64: CCA: Tear down RTTs Steven Price
2026-08-03 22:29   ` Alper Gun
2026-08-04 12:16     ` Suzuki K Poulose
2026-08-11 14:51       ` Suzuki K Poulose
2026-08-13 14:38         ` Steven Price
2026-08-03 13:43 ` [PATCH v16 18/45] KVM: arm64: CCA: Allocate and free RECs to match vCPUs Steven Price
2026-08-03 13:43 ` [PATCH v16 19/45] KVM: arm64: CCA: Support the VGIC in realms Steven Price
2026-08-03 13:43 ` [PATCH v16 20/45] KVM: arm64: CCA: Support timers in realm RECs Steven Price
2026-08-03 13:43 ` [PATCH v16 21/45] KVM: arm64: CCA: Handle realm enter/exit Steven Price
2026-08-04  8:57   ` Aneesh Kumar K.V
2026-08-13 14:38     ` Steven Price
2026-08-04 13:36   ` Aneesh Kumar K.V
2026-08-13 14:38     ` Steven Price
2026-08-10  8:03   ` Kohei Enju
2026-08-13 14:38     ` Steven Price
2026-08-03 13:43 ` [PATCH v16 22/45] KVM: arm64: CCA: Handle RMI_EXIT_RIPAS_CHANGE Steven Price
2026-08-05 15:59   ` Ackerley Tng
2026-08-06  8:42     ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 23/45] KVM: arm64: CCA: Handle realm MMIO emulation Steven Price
2026-08-03 13:43 ` [PATCH v16 24/45] KVM: arm64: Expose support for private memory Steven Price
2026-08-05 16:02   ` Ackerley Tng
2026-08-07 10:12     ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 25/45] KVM: arm64: CCA: Create the realm descriptor Steven Price
2026-08-03 13:43 ` [PATCH v16 26/45] KVM: arm64: CCA: Activate realms on first vCPU run Steven Price
2026-08-03 13:43 ` [PATCH v16 27/45] KVM: arm64: CCA: Allow populating initial contents Steven Price
2026-08-06 22:43   ` Ackerley Tng
2026-08-07 10:58     ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 28/45] KVM: arm64: CCA: Set RIPAS of initial memslots Steven Price
2026-08-03 13:43 ` [PATCH v16 29/45] KVM: arm64: CCA: Support runtime faulting of memory Steven Price
2026-08-06 23:11   ` Ackerley Tng
2026-08-11 15:42   ` Catalin Marinas
2026-08-12  9:01     ` Suzuki K Poulose
2026-08-12 14:06       ` Catalin Marinas
2026-08-12 15:40         ` Suzuki K Poulose
2026-08-03 13:43 ` [PATCH v16 30/45] KVM: arm64: CCA: Handle realm vCPU load Steven Price
2026-08-10 14:46   ` Kohei Enju
2026-08-03 13:43 ` [PATCH v16 31/45] KVM: arm64: CCA: Validate register access for Realm VMs Steven Price
2026-08-03 13:43 ` [PATCH v16 32/45] KVM: arm64: CCA: Handle Realm PSCI requests Steven Price
2026-08-03 13:43 ` [PATCH v16 33/45] KVM: arm64: WARN on injected undef exceptions Steven Price
2026-08-03 13:43 ` [PATCH v16 34/45] KVM: arm64: CCA: Allow userspace to inject aborts Steven Price
2026-08-03 13:43 ` [PATCH v16 35/45] KVM: arm64: CCA: Support RSI_HOST_CALL Steven Price
2026-08-03 13:43 ` [PATCH v16 36/45] KVM: arm64: CCA: Allow checking SVE on VM instance Steven Price
2026-08-03 13:43 ` [PATCH v16 37/45] KVM: arm64: CCA: Prevent Device mappings for realms Steven Price
2026-08-03 13:43 ` [PATCH v16 38/45] KVM: arm64: CCA: Propagate breakpoint and watchpoint counts to userspace Steven Price
2026-08-03 13:43 ` [PATCH v16 39/45] KVM: arm64: CCA: Set breakpoint parameters through SET_ONE_REG Steven Price
2026-08-03 13:43 ` [PATCH v16 40/45] KVM: arm64: CCA: Propagate max SVE vector length from the RMM Steven Price
2026-08-03 13:43 ` [PATCH v16 41/45] KVM: arm64: CCA: Configure max SVE vector length for a Realm Steven Price
2026-08-03 13:43 ` [PATCH v16 42/45] KVM: arm64: CCA: Provide register list for unfinalized RECs Steven Price
2026-08-03 13:43 ` [PATCH v16 43/45] KVM: arm64: CCA: Provide an accurate register list Steven Price
2026-08-03 13:44 ` [PATCH v16 44/45] KVM: arm64: CCA: Require ICH_HCR_EL2.TDIR for realms Steven Price
2026-08-10  4:58   ` Kohei Enju
2026-08-10  9:41     ` Marc Zyngier
2026-08-27 12:09       ` Kohei Enju
2026-08-24 14:50     ` Steven Price
2026-08-27 12:45       ` Kohei Enju
2026-08-03 13:44 ` [PATCH v16 45/45] KVM: arm64: CCA: Enable realms to be created Steven Price
2026-08-03 15:01 ` [PATCH v16 00/45] arm64: Support for Arm CCA in KVM Marc Zyngier
2026-08-03 15:06   ` Steven Price
2026-08-03 15:20     ` Marc Zyngier
2026-08-03 15:45       ` Steven Price
2026-08-04 14:24 ` Fuad Tabba
2026-08-06 22:05 ` Suzuki K Poulose
2026-08-11  4:44   ` Gavin Shan
2026-08-11 11:12     ` Suzuki K Poulose
2026-08-12  3:07       ` Gavin Shan
2026-08-12  3:25         ` Alper Gun
2026-08-12  6:04           ` Suzuki K Poulose
2026-08-12 10:35             ` Gavin Shan
2026-08-12 12:18               ` Suzuki K Poulose

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=551014ec-eafc-4a63-92f1-6efcf1ca4db1@redhat.com \
    --to=gshan@redhat.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=fj0570is@fujitsu.com \
    --cc=gankulkarni@os.amperecomputing.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=steven.price@arm.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