On Thu, 12 Oct 2023 21:51:08 +0100, Marc Zyngier wrote:
> We currently have a global VTCR_EL2 value for each guest, even
> if the guest uses NV. This implies that the guest's own S2 must
> fit in the host's. This is odd, for multiple reasons:
>
> - the PARange values and the number of IPA bits don't necessarily
> match: you can have 33 bits of IPA space, and yet you can only
> describe 32 or 36 bits of PARange
>
> [...]
Applied to kvmarm/next, thanks!
[1/1] KVM: arm64: Move VTCR_EL2 into struct s2_mmu
https://git.kernel.org/kvmarm/kvmarm/c/bff4906ad66a
--
Best,
Oliver
