linux.git/tools/testing/selftests/kvm/lib, branch v5.17

KVM: selftests: aarch64: Skip tests if we can't create a vgic-v3

2022-02-25T13:02:28+00:00

The arch_timer and vgic_irq kselftests assume that they can create a
vgic-v3, using the library function vgic_v3_setup() which aborts with a
test failure if it is not possible to do so. Since vgic-v3 can only be
instantiated on systems where the host has GICv3 this leads to false
positives on older systems where that is not the case.

Fix this by changing vgic_v3_setup() to return an error if the vgic can't
be instantiated and have the callers skip if this happens. We could also
exit flagging a skip in vgic_v3_setup() but this would prevent future test
cases conditionally deciding which GIC to use or generally doing more
complex output.

Signed-off-by: Mark Brown 
Reviewed-by: Andrew Jones 
Tested-by: Ricardo Koller 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220223131624.1830351-1-broonie@kernel.org

selftests: kvm: check dynamic bits against KVM_X86_XCOMP_GUEST_SUPP

2022-01-28T12:38:25+00:00

Provide coverage for the new API.

Signed-off-by: Paolo Bonzini

selftests: kvm: move vm_xsave_req_perm call to amx_test

2022-01-26T17:45:20+00:00

There is no need for tests other than amx_test to enable dynamic xsave
states.  Remove the call to vm_xsave_req_perm from generic code,
and move it inside the test.  While at it, allow customizing the bit
that is requested, so that future tests can use it differently.

Signed-off-by: Paolo Bonzini

selftests: kvm/x86: Fix the warning in lib/x86_64/processor.c

2022-01-20T17:12:47+00:00

The following warning appears when executing
make -C tools/testing/selftests/kvm

include/x86_64/processor.h:290:2: warning: 'ecx' may be used uninitialized in this
function [-Wmaybe-uninitialized]
  asm volatile("cpuid"
  ^~~
lib/x86_64/processor.c:1523:21: note: 'ecx' was declared here
  uint32_t eax, ebx, ecx, edx, max_ext_leaf;

Just initialize ecx to remove this warning.

Fixes: c8cc43c1eae2 ("selftests: KVM: avoid failures due to reserved HyperTransport region")
Signed-off-by: Jinrong Liang 
Message-Id: <20220119140325.59369-1-cloudliang@tencent.com>
Signed-off-by: Paolo Bonzini

kvm: selftests: Do not indent with spaces

2022-01-19T18:34:30+00:00

Some indentation with spaces crept in, likely due to terminal-based
cut and paste.  Clean it up.

Signed-off-by: Paolo Bonzini

selftests: kvm/x86: Export x86_family() for use outside of processor.c

2022-01-19T17:12:03+00:00

Move this static inline function to processor.h, so that it can be
used in individual tests, as needed.

Opportunistically replace the bare 'unsigned' with 'unsigned int.'

Signed-off-by: Jim Mattson 
Signed-off-by: Paolo Bonzini 
Message-Id: <20220115052431.447232-5-jmattson@google.com>
Signed-off-by: Paolo Bonzini

selftests: kvm/x86: Introduce is_amd_cpu()

2022-01-19T17:11:43+00:00

Replace the one ad hoc "AuthenticAMD" CPUID vendor string comparison
with a new function, is_amd_cpu().

Signed-off-by: Jim Mattson 
Signed-off-by: Paolo Bonzini 
Message-Id: <20220115052431.447232-4-jmattson@google.com>
Signed-off-by: Paolo Bonzini

selftests: kvm/x86: Parameterize the CPUID vendor string check

2022-01-19T17:11:40+00:00

Refactor is_intel_cpu() to make it easier to reuse the bulk of the
code for other vendors in the future.

Signed-off-by: Jim Mattson 
Signed-off-by: Paolo Bonzini 
Message-Id: <20220115052431.447232-3-jmattson@google.com>
Signed-off-by: Paolo Bonzini

kvm: selftests: conditionally build vm_xsave_req_perm()

2022-01-19T17:09:25+00:00

vm_xsave_req_perm() is currently defined and used by x86_64 only.
Make it compiled into vm_create_with_vcpus() only when on x86_64
machines. Otherwise, it would cause linkage errors, e.g. on s390x.

Fixes: 415a3c33e8 ("kvm: selftests: Add support for KVM_CAP_XSAVE2")
Reported-by: Janis Schoetterl-Glausch 
Signed-off-by: Wei Wang 
Tested-by: Janis Schoetterl-Glausch 
Message-Id: <20220118014817.30910-1-wei.w.wang@intel.com>
Signed-off-by: Paolo Bonzini

KVM: selftests: Test KVM_SET_CPUID2 after KVM_RUN

2022-01-17T17:30:24+00:00

KVM forbids KVM_SET_CPUID2 after KVM_RUN was performed on a vCPU unless
the supplied CPUID data is equal to what was previously set. Test this.

Signed-off-by: Vitaly Kuznetsov 
Message-Id: <20220117150542.2176196-5-vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini