<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/tools/testing/selftests/kvm/aarch64, branch linux-5.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-04-27T12:41:07Z</updated>
<entry>
<title>selftests: KVM: Free the GIC FD when cleaning up in arch_timer</title>
<updated>2022-04-27T12:41:07Z</updated>
<author>
<name>Oliver Upton</name>
</author>
<published>2022-04-06T23:56:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f828c2d4f07872cbbef0b4c13ee67bb588a2da8f'/>
<id>urn:sha1:f828c2d4f07872cbbef0b4c13ee67bb588a2da8f</id>
<content type='text'>
[ Upstream commit 21db83846683d3987666505a3ec38f367708199a ]

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 &lt;oupton@google.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20220406235615.1447180-4-oupton@google.com
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>kvm: selftests: aarch64: fix some vgic related comments</title>
<updated>2022-04-13T17:27:13Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2022-01-27T03:08:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b6ca260912abe87d1ddc6cf0b81622282e50bb3f'/>
<id>urn:sha1:b6ca260912abe87d1ddc6cf0b81622282e50bb3f</id>
<content type='text'>
[ Upstream commit a5cd38fd9c47b23abc6df08d6ee6a71b39038185 ]

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

Signed-off-by: Ricardo Koller &lt;ricarkol@google.com&gt;
Reported-by: Reiji Watanabe &lt;reijiw@google.com&gt;
Cc: Andrew Jones &lt;drjones@redhat.com&gt;
Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20220127030858.3269036-5-ricarkol@google.com
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>kvm: selftests: aarch64: fix the failure check in kvm_set_gsi_routing_irqchip_check</title>
<updated>2022-04-13T17:27:13Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2022-01-27T03:08:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8b008164c8f583201b31d6d34480db1dcc0dc2d9'/>
<id>urn:sha1:8b008164c8f583201b31d6d34480db1dcc0dc2d9</id>
<content type='text'>
[ Upstream commit 5b7898648f02083012900e48d063e51ccbdad165 ]

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 &gt;= KVM_IRQCHIP_NUM_PINS", so
kvm_set_gsi_routing_irqchip_check() should test the error only when
"intid &gt;= KVM_IRQCHIP_NUM_PINS+32". The issue is that the test check is
"intid &gt;= 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 &lt;ricarkol@google.com&gt;
Reported-by: Reiji Watanabe &lt;reijiw@google.com&gt;
Cc: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20220127030858.3269036-4-ricarkol@google.com
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>kvm: selftests: aarch64: pass vgic_irq guest args as a pointer</title>
<updated>2022-04-13T17:27:13Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2022-01-27T03:08:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=535a76f309d15f37252cd17155da36226823286f'/>
<id>urn:sha1:535a76f309d15f37252cd17155da36226823286f</id>
<content type='text'>
[ Upstream commit 11024a7a0ac26dd31ddfa0f6590e158bdf9ab858 ]

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 &lt;ricarkol@google.com&gt;
Reported-by: Reiji Watanabe &lt;reijiw@google.com&gt;
Cc: Andrew Jones &lt;drjones@redhat.com&gt;
Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20220127030858.3269036-3-ricarkol@google.com
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>KVM: selftests: aarch64: Skip tests if we can't create a vgic-v3</title>
<updated>2022-02-25T13:02:28Z</updated>
<author>
<name>Mark Brown</name>
</author>
<published>2022-02-23T13:16:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=456f89e0928ab938122a40e9f094a6524cc158b4'/>
<id>urn:sha1:456f89e0928ab938122a40e9f094a6524cc158b4</id>
<content type='text'>
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 &lt;broonie@kernel.org&gt;
Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt;
Tested-by: Ricardo Koller &lt;ricarkol@google.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20220223131624.1830351-1-broonie@kernel.org
</content>
</entry>
<entry>
<title>Merge branch kvm-arm64/misc-5.17 into kvmarm-master/next</title>
<updated>2022-01-04T17:16:15Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2022-01-04T17:16:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1c53a1ae36120997a82f936d044c71075852e521'/>
<id>urn:sha1:1c53a1ae36120997a82f936d044c71075852e521</id>
<content type='text'>
* kvm-arm64/misc-5.17:
  : .
  : Misc fixes and improvements:
  : - Add minimal support for ARMv8.7's PMU extension
  : - Constify kvm_io_gic_ops
  : - Drop kvm_is_transparent_hugepage() prototype
  : - Drop unused workaround_flags field
  : - Rework kvm_pgtable initialisation
  : - Documentation fixes
  : - Replace open-coded SCTLR_EL1.EE useage with its defined macro
  : - Sysreg list selftest update to handle PAuth
  : - Include cleanups
  : .
  KVM: arm64: vgic: Replace kernel.h with the necessary inclusions
  KVM: arm64: Fix comment typo in kvm_vcpu_finalize_sve()
  KVM: arm64: selftests: get-reg-list: Add pauth configuration
  KVM: arm64: Fix comment on barrier in kvm_psci_vcpu_on()
  KVM: arm64: Fix comment for kvm_reset_vcpu()
  KVM: arm64: Use defined value for SCTLR_ELx_EE
  KVM: arm64: Rework kvm_pgtable initialisation
  KVM: arm64: Drop unused workaround_flags vcpu field

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
</content>
</entry>
<entry>
<title>KVM: arm64: selftests: get-reg-list: Add pauth configuration</title>
<updated>2022-01-04T13:39:55Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2021-12-28T12:14:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f15dcf1b5853e770ed614e23ab2e90f0ca1b7b0b'/>
<id>urn:sha1:f15dcf1b5853e770ed614e23ab2e90f0ca1b7b0b</id>
<content type='text'>
The get-reg-list test ignores the Pointer Authentication features,
which is a shame now that we have relatively common HW with this feature.

Define two new configurations (with and without PMU) that exercise the
KVM capabilities.

Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt;
Link: https://lore.kernel.org/r/20211228121414.1013250-1-maz@kernel.org
</content>
</entry>
<entry>
<title>KVM: selftests: aarch64: Add test for restoring active IRQs</title>
<updated>2021-12-28T19:25:05Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2021-11-09T02:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=728fcc46d2c2292d1ac73f3491b8f4332066fdad'/>
<id>urn:sha1:728fcc46d2c2292d1ac73f3491b8f4332066fdad</id>
<content type='text'>
Add a test that restores multiple IRQs in active state, it does it by
writing into ISACTIVER from the guest and using KVM ioctls. This test
tries to emulate what would happen during a live migration: restore
active IRQs.

Signed-off-by: Ricardo Koller &lt;ricarkol@google.com&gt;
Acked-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20211109023906.1091208-18-ricarkol@google.com
</content>
</entry>
<entry>
<title>KVM: selftests: aarch64: Add ISPENDR write tests in vgic_irq</title>
<updated>2021-12-28T19:25:00Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2021-11-09T02:39:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bebd8f3f869361e0249efe423ba76a0d991ce3e6'/>
<id>urn:sha1:bebd8f3f869361e0249efe423ba76a0d991ce3e6</id>
<content type='text'>
Add injection tests that use writing into the ISPENDR register (to mark
IRQs as pending). This is typically used by migration code.

Signed-off-by: Ricardo Koller &lt;ricarkol@google.com&gt;
Acked-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20211109023906.1091208-17-ricarkol@google.com
</content>
</entry>
<entry>
<title>KVM: selftests: aarch64: Add tests for IRQFD in vgic_irq</title>
<updated>2021-12-28T19:24:54Z</updated>
<author>
<name>Ricardo Koller</name>
</author>
<published>2021-11-09T02:39:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a5a47188caca7be4bbe28cdb31d5df09868ed5c'/>
<id>urn:sha1:6a5a47188caca7be4bbe28cdb31d5df09868ed5c</id>
<content type='text'>
Add injection tests for the KVM_IRQFD ioctl into vgic_irq.

Signed-off-by: Ricardo Koller &lt;ricarkol@google.com&gt;
Acked-by: Andrew Jones &lt;drjones@redhat.com&gt;
Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;
Link: https://lore.kernel.org/r/20211109023906.1091208-16-ricarkol@google.com
</content>
</entry>
</feed>
