linux-toradex.git/tools/testing/selftests/kvm/aarch64, branch v5.18

selftests: KVM: Free the GIC FD when cleaning up in arch_timer

2022-04-07T07:46:13+00:00

In order to correctly destroy a VM, all references to the VM must be
freed. The arch_timer selftest creates a VGIC for the guest, which
itself holds a reference to the VM.

Close the GIC FD when cleaning up a VM.

Signed-off-by: Oliver Upton 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220406235615.1447180-4-oupton@google.com

KVM: selftests: get-reg-list: Add KVM_REG_ARM_FW_REG(3)

2022-04-07T07:45:01+00:00

When testing a kernel with commit a5905d6af492 ("KVM: arm64:
Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated")
get-reg-list output

vregs: Number blessed registers:   234
vregs: Number registers:           238

vregs: There are 1 new registers.
Consider adding them to the blessed reg list with the following lines:

	KVM_REG_ARM_FW_REG(3),

vregs: PASS
...

That output inspired two changes: 1) add the new register to the
blessed list and 2) explain why "Number registers" is actually four
larger than "Number blessed registers" (on the system used for
testing), even though only one register is being stated as new.
The reason is that some registers are host dependent and they get
filtered out when comparing with the blessed list. The system
used for the test apparently had three filtered registers.

Signed-off-by: Andrew Jones 
Acked-by: Marc Zyngier 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220316125129.392128-1-drjones@redhat.com

KVM: arm64: selftests: Introduce vcpu_width_config

2022-04-06T11:29:45+00:00

Introduce a test for aarch64 that ensures non-mixed-width vCPUs
(all 64bit vCPUs or all 32bit vcPUs) can be configured, and
mixed-width vCPUs cannot be configured.

Reviewed-by: Andrew Jones 
Signed-off-by: Reiji Watanabe 
Reviewed-by: Oliver Upton 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220329031924.619453-3-reijiw@google.com

Merge tag 'kvmarm-5.18' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD

2022-03-18T16:43:24+00:00

KVM/arm64 updates for 5.18

- Proper emulation of the OSLock feature of the debug architecture

- Scalibility improvements for the MMU lock when dirty logging is on

- New VMID allocator, which will eventually help with SVA in VMs

- Better support for PMUs in heterogenous systems

- PSCI 1.1 support, enabling support for SYSTEM_RESET2

- Implement CONFIG_DEBUG_LIST at EL2

- Make CONFIG_ARM64_ERRATUM_2077057 default y

- Reduce the overhead of VM exit when no interrupt is pending

- Remove traces of 32bit ARM host support from the documentation

- Updated vgic selftests

- Various cleanups, doc updates and spelling fixes

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

Merge branch kvm-arm64/selftest/vgic-5.18 into kvmarm-master/next

2022-02-08T15:20:16+00:00

* kvm-arm64/selftest/vgic-5.18:
  : .
  : A bunch of selftest fixes, courtesy of Ricardo Koller
  : .
  kvm: selftests: aarch64: use a tighter assert in vgic_poke_irq()
  kvm: selftests: aarch64: fix some vgic related comments
  kvm: selftests: aarch64: fix the failure check in kvm_set_gsi_routing_irqchip_check
  kvm: selftests: aarch64: pass vgic_irq guest args as a pointer
  kvm: selftests: aarch64: fix assert in gicv3_access_reg

Signed-off-by: Marc Zyngier

kvm: selftests: aarch64: fix some vgic related comments

2022-02-08T15:18:58+00:00

Fix the formatting of some comments and the wording of one of them (in
gicv3_access_reg).

Signed-off-by: Ricardo Koller 
Reported-by: Reiji Watanabe 
Cc: Andrew Jones 
Reviewed-by: Andrew Jones 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220127030858.3269036-5-ricarkol@google.com

kvm: selftests: aarch64: fix the failure check in kvm_set_gsi_routing_irqchip_check

2022-02-08T15:18:58+00:00

kvm_set_gsi_routing_irqchip_check(expect_failure=true) is used to check
the error code returned by the kernel when trying to setup an invalid
gsi routing table. The ioctl fails if "pin >= KVM_IRQCHIP_NUM_PINS", so
kvm_set_gsi_routing_irqchip_check() should test the error only when
"intid >= KVM_IRQCHIP_NUM_PINS+32". The issue is that the test check is
"intid >= KVM_IRQCHIP_NUM_PINS", so for a case like "intid =
KVM_IRQCHIP_NUM_PINS" the test wrongly assumes that the kernel will
return an error.  Fix this by using the right check.

Signed-off-by: Ricardo Koller 
Reported-by: Reiji Watanabe 
Cc: Andrew Jones 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220127030858.3269036-4-ricarkol@google.com

kvm: selftests: aarch64: pass vgic_irq guest args as a pointer

2022-02-08T15:18:58+00:00

The guest in vgic_irq gets its arguments in a struct. This struct used
to fit nicely in a single register so vcpu_args_set() was able to pass
it by value by setting x0 with it. Unfortunately, this args struct grew
after some commits and some guest args became random (specically
kvm_supports_irqfd).

Fix this by passing the guest args as a pointer (after allocating some
guest memory for it).

Signed-off-by: Ricardo Koller 
Reported-by: Reiji Watanabe 
Cc: Andrew Jones 
Reviewed-by: Andrew Jones 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220127030858.3269036-3-ricarkol@google.com

selftests: KVM: Test OS lock behavior

2022-02-08T14:23:41+00:00

KVM now correctly handles the OS Lock for its guests. When set, KVM
blocks all debug exceptions originating from the guest. Add test cases
to the debug-exceptions test to assert that software breakpoint,
hardware breakpoint, watchpoint, and single-step exceptions are in fact
blocked.

Signed-off-by: Oliver Upton 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220203174159.2887882-7-oupton@google.com