On Mon, 4 Oct 2021 18:19:10 -0700, Ricardo Koller wrote:
> KVM doesn't check for redist, CPU interface, and ITS regions that extend
> partially above the guest addressable IPA range (phys_size). This can happen
> when using the V[2|3]_ADDR_TYPE_CPU, ADDR_TYPE_REDIST[_REGION], or
> ITS_ADDR_TYPE attributes to set a new region that extends partially above
> phys_size (with the base below phys_size). The issue is that vcpus can
> potentially run into a situation where some redistributors are addressable and
> others are not, or just the first half of the ITS is addressable.
>
> [...]
Applied to next, thanks!
[01/11] kvm: arm64: vgic: Introduce vgic_check_iorange
commit: f25c5e4dafd859b941a4654cbab9eb83ff994bcd
[02/11] KVM: arm64: vgic-v3: Check redist region is not above the VM IPA size
commit: 4612d98f58c73ad63928200fd332f75c8e524dae
[03/11] KVM: arm64: vgic-v2: Check cpu interface region is not above the VM IPA size
commit: c56a87da0a7fa14180082249ac954c7ebc9e74e1
[04/11] KVM: arm64: vgic-v3: Check ITS region is not above the VM IPA size
commit: 2ec02f6c64f043a249850c835ca7975c3a155d8b
[05/11] KVM: arm64: vgic: Drop vgic_check_ioaddr()
commit: 96e903896969679104c7fef2c776ed1b5b09584f
[06/11] KVM: arm64: selftests: Make vgic_init gic version agnostic
commit: 3f4db37e203b0562d9ebae575af13ea159fbd077
[07/11] KVM: arm64: selftests: Make vgic_init/vm_gic_create version agnostic
commit: 46fb941bc04d3541776c09c2bf641e7f34e62a01
[08/11] KVM: arm64: selftests: Add some tests for GICv2 in vgic_init
commit: c44df5f9ff31daaa72b3a673422d5cca03a1fd02
[09/11] KVM: arm64: selftests: Add tests for GIC redist/cpuif partially above IPA range
commit: 2dcd9aa1c3a5d3c90047d67efd08f0518f915449
[10/11] KVM: arm64: selftests: Add test for legacy GICv3 REDIST base partially above IPA range
commit: 1883458638979531fc4fcbc26d15fec3e51e1734
[11/11] KVM: arm64: selftests: Add init ITS device test
commit: 3e197f17b23ba7c1a3c7cb1d27f7494444aa42e3
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
