[PATCH v17 03/20] KVM: arm64: Track the type of VM in kvm_arch
Gavin Shan
gshan at redhat.com
Wed Sep 9 20:39:36 PDT 2026
Hi Suzuki,
On 9/9/26 2:22 AM, Suzuki K Poulose wrote:
> KVM arm64 has different types of VMs with all the different modes in which the
> hypervisor code can be run. e.g., VHE, nVHE, PKVM etc. Then there is protected
> VM and normal VMs with PKVM. We might soon add other types, e.g., Arm CCA Realm.
> So in an effort to make the handling of these different types of VMs a bit more
> friendlier to the eyes, add a VM flavor to the kvm_arch and we could then add
> handlers for different operations based on the VM type.
>
> Keep the flavor initialisation at the beginning to allow for the detection
> early enough and fail out on any unsupported requests. (e.g., protected on !PKVM)
>
> With that, use the vm_flavor to detect if a VM is protected VM on PKVM.
>
> Based on a patch by Marc Zyngier
>
> Suggested-by: Marc Zyngier <maz at kernel.org>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose at arm.com>
> ---
> arch/arm64/include/asm/kvm_host.h | 12 ++++++++++--
> arch/arm64/kvm/arm.c | 27 ++++++++++++++++++++++++---
> arch/arm64/kvm/hyp/nvhe/pkvm.c | 2 +-
> arch/arm64/kvm/pkvm.c | 1 -
> 4 files changed, 35 insertions(+), 7 deletions(-)
>
Some nitpicks below. In either way:
Reviewed-by: Gavin Shan <gshan at redhat.com>
> diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
> index 27fe0cd5b2d7a..d0dccc9ad6aa8 100644
> --- a/arch/arm64/include/asm/kvm_host.h
> +++ b/arch/arm64/include/asm/kvm_host.h
> @@ -257,7 +257,6 @@ struct kvm_protected_vm {
> pkvm_handle_t handle;
> struct kvm_hyp_memcache teardown_mc;
> struct kvm_hyp_memcache stage2_teardown_mc;
> - bool is_protected;
> bool is_created;
>
> /*
> @@ -306,9 +305,18 @@ enum fgt_group_id {
> __NR_FGT_GROUP_IDS__
> };
>
> +enum kvm_arm_vm_flavor {
> + VM_NVHE,
> + VM_VHE,
> + VM_PKVM, /* Normal guests on PKVM */
> + VM_PROTECTED_PKVM, /* Protected VM */
> + VM_FLAVOR_MAX,
> +};
> +
> struct kvm_arch {
> struct kvm_s2_mmu mmu;
>
> + enum kvm_arm_vm_flavor vm_flavor;
> /*
> * Fine-Grained UNDEF, mimicking the FGT layout defined by the
> * architecture. We track them globally, as we present the
> @@ -1504,7 +1512,7 @@ struct kvm *kvm_arch_alloc_vm(void);
>
> #define __KVM_HAVE_ARCH_FLUSH_REMOTE_TLBS_RANGE
>
> -#define kvm_vm_is_protected(kvm) (is_protected_kvm_enabled() && (kvm)->arch.pkvm.is_protected)
> +#define kvm_vm_is_protected(kvm) ((kvm)->arch.vm_flavor == VM_PROTECTED_PKVM)
>
Here we may introduce one more helper for generic use cases. It's going to
be used in kvm_arch_init_vm().
#define kvm_vm_flavor_eq(kvm, flavor) ((kvm)->arch.vm_flaor == (flavor))
#define kvm_vm_is_protected(kvm) kvm_vm_flavor_eq(kvm, VM_PROTECTED_PKVM)
> #define vcpu_is_protected(vcpu) kvm_vm_is_protected((vcpu)->kvm)
>
> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> index 8b080804bc90b..67f1ff9bc4fbe 100644
> --- a/arch/arm64/kvm/arm.c
> +++ b/arch/arm64/kvm/arm.c
> @@ -214,6 +214,26 @@ static int kvm_arm_default_max_vcpus(void)
> return vgic_present ? kvm_vgic_get_max_vcpus() : KVM_MAX_VCPUS;
> }
>
> +static int kvm_init_vm_flavor(struct kvm *kvm, unsigned long type)
> +{
> + bool protected = type & KVM_VM_TYPE_ARM_PROTECTED;
> +
> + if (is_protected_kvm_enabled()) {
> + if (protected)
> + kvm->arch.vm_flavor = VM_PROTECTED_PKVM;
> + else
> + kvm->arch.vm_flavor = VM_PKVM;
> + } else if (protected) {
> + return -EINVAL;
> + } else if (has_vhe()) {
> + kvm->arch.vm_flavor = VM_VHE;
> + } else {
> + kvm->arch.vm_flavor = VM_NVHE;
> + }
> +
> + return 0;
> +}
> +
> /**
> * kvm_arch_init_vm - initializes a VM data structure
> * @kvm: pointer to the KVM struct
> @@ -236,6 +256,10 @@ int kvm_arch_init_vm(struct kvm *kvm, unsigned long type)
> mutex_unlock(&kvm->lock);
> #endif
>
> + ret = kvm_init_vm_flavor(kvm, type);
> + if (ret)
> + return ret;
> +
> kvm_init_nested(kvm);
>
> ret = kvm_share_hyp(kvm, kvm + 1);
> @@ -260,9 +284,6 @@ int kvm_arch_init_vm(struct kvm *kvm, unsigned long type)
> ret = pkvm_init_host_vm(kvm, type);
> if (ret)
> goto err_uninit_mmu;
> - } else if (type & KVM_VM_TYPE_ARM_PROTECTED) {
> - ret = -EINVAL;
> - goto err_uninit_mmu;
> }
>
> kvm_vgic_early_init(kvm);
We needn't depend on is_protected_kvm_enabled() to call pkvm_init_host_vm() because
the output of is_protected_kvm_enabled() has been updated to kvm->arch.vm_flavor
by previous call kvm_init_vm_flavor().
if (kvm_vm_is_protected(kvm) || kvm_vm_flavor_eq(kvm, VM_PKVM)) {
ret = pkvm_init_host_vm(kvm, type);
if (ret)
goto err_unit_mmu;
}
> diff --git a/arch/arm64/kvm/hyp/nvhe/pkvm.c b/arch/arm64/kvm/hyp/nvhe/pkvm.c
> index 459bd9eb7e4bc..09961c0056f2b 100644
> --- a/arch/arm64/kvm/hyp/nvhe/pkvm.c
> +++ b/arch/arm64/kvm/hyp/nvhe/pkvm.c
> @@ -432,7 +432,7 @@ static void init_pkvm_hyp_vm(struct kvm *host_kvm, struct pkvm_hyp_vm *hyp_vm,
>
> hyp_vm->host_kvm = host_kvm;
> hyp_vm->kvm.created_vcpus = nr_vcpus;
> - hyp_vm->kvm.arch.pkvm.is_protected = READ_ONCE(host_kvm->arch.pkvm.is_protected);
> + hyp_vm->kvm.arch.vm_flavor = READ_ONCE(host_kvm->arch.vm_flavor);
> hyp_vm->kvm.arch.flags = 0;
> pkvm_init_features_from_host(hyp_vm, host_kvm);
>
> diff --git a/arch/arm64/kvm/pkvm.c b/arch/arm64/kvm/pkvm.c
> index 8e4c6e4bec123..3948fa46f4d75 100644
> --- a/arch/arm64/kvm/pkvm.c
> +++ b/arch/arm64/kvm/pkvm.c
> @@ -240,7 +240,6 @@ int pkvm_init_host_vm(struct kvm *kvm, unsigned long type)
> return ret;
>
> kvm->arch.pkvm.handle = ret;
> - kvm->arch.pkvm.is_protected = protected;
> if (protected) {
> pr_warn_once("kvm: protected VMs are experimental and for development only, tainting kernel\n");
> add_taint(TAINT_USER, LOCKDEP_STILL_OK);
In pkvm_init_host_vm(), the local variable 'protected' is used for once
and can be removed by:
if (kvm_vm_is_protected(kvm)) {
pr_warn_once(...);
add_taint(...);
}
Thanks,
Gavin
More information about the linux-arm-kernel
mailing list