mirror of
https://github.com/raspberrypi/linux.git
synced 2025-12-19 16:24:21 +00:00
67730e6c53
Use the kernel's canonical $(ARCH) paths instead of the raw target triple for KVM selftests directories. KVM selftests are quite nearly the only place in the entire kernel that using the target triple for directories, tools/testing/selftests/drivers/s390x being the lone holdout. Using the kernel's preferred nomenclature eliminates the minor, but annoying, friction of having to translate to KVM's selftests directories, e.g. for pattern matching, opening files, running selftests, etc. Opportunsitically delete file comments that reference the full path of the file, as they are obviously prone to becoming stale, and serve no known purpose. Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com> Acked-by: Claudio Imbrenda <imbrenda@linux.ibm.com> Acked-by: Andrew Jones <ajones@ventanamicro.com> Link: https://lore.kernel.org/r/20241128005547.4077116-16-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
63 lines
1.8 KiB
C
63 lines
1.8 KiB
C
// SPDX-License-Identifier: GPL-2.0-only
|
|
/*
|
|
* maximum APIC ID capability tests
|
|
*
|
|
* Copyright (C) 2022, Intel, Inc.
|
|
*
|
|
* Tests for getting/setting maximum APIC ID capability
|
|
*/
|
|
|
|
#include "kvm_util.h"
|
|
|
|
#define MAX_VCPU_ID 2
|
|
|
|
int main(int argc, char *argv[])
|
|
{
|
|
struct kvm_vm *vm;
|
|
int ret;
|
|
|
|
vm = vm_create_barebones();
|
|
|
|
/* Get KVM_CAP_MAX_VCPU_ID cap supported in KVM */
|
|
ret = vm_check_cap(vm, KVM_CAP_MAX_VCPU_ID);
|
|
|
|
/* Try to set KVM_CAP_MAX_VCPU_ID beyond KVM cap */
|
|
ret = __vm_enable_cap(vm, KVM_CAP_MAX_VCPU_ID, ret + 1);
|
|
TEST_ASSERT(ret < 0,
|
|
"Setting KVM_CAP_MAX_VCPU_ID beyond KVM cap should fail");
|
|
|
|
/* Test BOOT_CPU_ID interaction (MAX_VCPU_ID cannot be lower) */
|
|
if (kvm_has_cap(KVM_CAP_SET_BOOT_CPU_ID)) {
|
|
vm_ioctl(vm, KVM_SET_BOOT_CPU_ID, (void *)MAX_VCPU_ID);
|
|
|
|
/* Try setting KVM_CAP_MAX_VCPU_ID below BOOT_CPU_ID */
|
|
ret = __vm_enable_cap(vm, KVM_CAP_MAX_VCPU_ID, MAX_VCPU_ID - 1);
|
|
TEST_ASSERT(ret < 0,
|
|
"Setting KVM_CAP_MAX_VCPU_ID below BOOT_CPU_ID should fail");
|
|
}
|
|
|
|
/* Set KVM_CAP_MAX_VCPU_ID */
|
|
vm_enable_cap(vm, KVM_CAP_MAX_VCPU_ID, MAX_VCPU_ID);
|
|
|
|
/* Try to set KVM_CAP_MAX_VCPU_ID again */
|
|
ret = __vm_enable_cap(vm, KVM_CAP_MAX_VCPU_ID, MAX_VCPU_ID + 1);
|
|
TEST_ASSERT(ret < 0,
|
|
"Setting KVM_CAP_MAX_VCPU_ID multiple times should fail");
|
|
|
|
/* Create vCPU with id beyond KVM_CAP_MAX_VCPU_ID cap */
|
|
ret = __vm_ioctl(vm, KVM_CREATE_VCPU, (void *)MAX_VCPU_ID);
|
|
TEST_ASSERT(ret < 0, "Creating vCPU with ID > MAX_VCPU_ID should fail");
|
|
|
|
/* Create vCPU with bits 63:32 != 0, but an otherwise valid id */
|
|
ret = __vm_ioctl(vm, KVM_CREATE_VCPU, (void *)(1L << 32));
|
|
TEST_ASSERT(ret < 0, "Creating vCPU with ID[63:32] != 0 should fail");
|
|
|
|
/* Create vCPU with id within bounds */
|
|
ret = __vm_ioctl(vm, KVM_CREATE_VCPU, (void *)0);
|
|
TEST_ASSERT(ret >= 0, "Creating vCPU with ID 0 should succeed");
|
|
|
|
close(ret);
|
|
kvm_vm_free(vm);
|
|
return 0;
|
|
}
|