The ioctls have been implemented, allow the userspace to lock and unlock
memslots.

Signed-off-by: Alexandru Elisei <alexandru.eli...@arm.com>
---
 arch/arm64/kvm/arm.c | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
index 13f3af1f2e78..27e86e480355 100644
--- a/arch/arm64/kvm/arm.c
+++ b/arch/arm64/kvm/arm.c
@@ -78,11 +78,6 @@ int kvm_arch_check_processor_compat(void *opaque)
        return 0;
 }
 
-static int kvm_arm_lock_memslot_supported(void)
-{
-       return 0;
-}
-
 static int kvm_lock_user_memory_region_ioctl(struct kvm *kvm,
                                             struct kvm_enable_cap *cap)
 {
@@ -129,8 +124,6 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm,
                mutex_unlock(&kvm->lock);
                break;
        case KVM_CAP_ARM_LOCK_USER_MEMORY_REGION:
-               if (!kvm_arm_lock_memslot_supported())
-                       return -EINVAL;
                r = kvm_lock_user_memory_region_ioctl(kvm, cap);
                break;
        default:
@@ -308,7 +301,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
                r = system_has_full_ptr_auth();
                break;
        case KVM_CAP_ARM_LOCK_USER_MEMORY_REGION:
-               r = kvm_arm_lock_memslot_supported();
+               r = 1;
                break;
        default:
                r = 0;
-- 
2.33.1

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

Reply via email to