summaryrefslogtreecommitdiffstats
path: root/arch/arm64/include
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2020-04-27 15:15:07 +0100
committerMarc Zyngier <maz@kernel.org>2020-05-16 15:05:02 +0100
commit5107000faa6e8c2b0ff7a91a6d1f010f84596cd2 (patch)
tree5b45fc529c5d6a17f0d11e15c9fc3ca87c2a3a08 /arch/arm64/include
parentc862626e19efdc26b26481515470b160e8fe52f3 (diff)
KVM: arm64: Make KVM_CAP_MAX_VCPUS compatible with the selected GIC version
KVM_CAP_MAX_VCPUS always return the maximum possible number of VCPUs, irrespective of the selected interrupt controller. This is pretty misleading for userspace that selects a GICv2 on a GICv3 system that supports v2 compat: It always gets a maximum of 512 VCPUs, even if the effective limit is 8. The 9th VCPU will fail to be created, which is unexpected as far as userspace is concerned. Fortunately, we already have the right information stashed in the kvm structure, and we can return it as requested. Reported-by: Ard Biesheuvel <ardb@kernel.org> Signed-off-by: Marc Zyngier <maz@kernel.org> Tested-by: Alexandru Elisei <alexandru.elisei@arm.com> Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com> Link: https://lore.kernel.org/r/20200427141507.284985-1-maz@kernel.org
Diffstat (limited to 'arch/arm64/include')
0 files changed, 0 insertions, 0 deletions