On Mon, 13 May 2024 09:40:03 +0800, Tao Su wrote:
> Use the max mappable GPA via GuestPhysBits advertised by KVM to calculate
> max_gfn. Currently some selftests (e.g. access_tracking_perf_test,
> dirty_log_test...) add RAM regions close to max_gfn, so guest may access
> GPA beyond its mappable range and cause infinite loop.
>
> Adjust max_gfn in vm_compute_max_gfn() since x86 selftests already
> overrides vm_compute_max_gfn() specifically to deal with goofy edge cases.
>
> [...]
Applied to kvm-x86 fixes, thanks!
[1/1] KVM: selftests: x86: Prioritize getting max_gfn from GuestPhysBits
https://github.com/kvm-x86/linux/commit/b24f5cf7b2ae
--
https://github.com/kvm-x86/linux/tree/next
