On Wed, 08 May 2024 07:19:52 +0000, Oliver Upton wrote:
> A particularly annoying userspace could create a vCPU after KVM has
> computed mpidr_data for the VM, either by racing against VGIC
> initialization or having a userspace irqchip.
>
> In any case, this means mpidr_data no longer fully describes the VM, and
> attempts to find the new vCPU with kvm_mpidr_to_vcpu() will fail. The
> fix is to discard mpidr_data altogether, as it is only a performance
> optimization and not required for correctness. In all likelihood KVM
> will recompute the mappings when KVM_RUN is called on the new vCPU.
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Destroy mpidr_data for 'late' vCPU creation
commit: ce5d2448eb8fe83aed331db53a08612286a137dd
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
