On Mon, 22 Nov 2021 12:18:40 +0000, Shameer Kolothum wrote:
> Changes from v3:
> - Main change is in patch #4, where the VMID is now set to an
> invalid one on vCPU schedule out. Introduced an
> INVALID_ACTIVE_VMID which is basically a VMID 0 with generation 1.
> Since the basic allocator algorithm reserves vmid #0, it is never
> used as an active VMID. This (hopefully) will fix the issue of
> unnecessarily reserving VMID space with active_vmids when those
> VMs are no longer active[0] and at the same time address the
> problem noted in v3 wherein everything ends up in slow-path[1].
>
> [...]
Applied to next, thanks!
[1/4] KVM: arm64: Introduce a new VMID allocator for KVM
commit: 417838392f2e657ee25cc30e373ff4c35a0faa90
[2/4] KVM: arm64: Make VMID bits accessible outside of allocator
commit: f8051e960922a9de8e42159103d5d9c697ef17ec
[3/4] KVM: arm64: Align the VMID allocation with the arm64 ASID
commit: 3248136b3637e1671e4fa46e32e2122f9ec4bc3d
[4/4] KVM: arm64: Make active_vmids invalid on vCPU schedule out
commit: 100b4f092f878dc379f1fcef9ce567c25dee3473
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
