diff options
author | Tao Su <tao1.su@linux.intel.com> | 2024-05-13 09:40:03 +0800 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2024-06-05 06:16:10 -0700 |
commit | 980b8bc01938c8bcc9742c1051f64b5f0ed178ac (patch) | |
tree | 0bf3dfac527077cb2f266b669c86250eebdad8ab /lib/ubsan.c | |
parent | d21b3c60d6e3917f7388db6bcc455f01c99ee42b (diff) |
KVM: selftests: x86: Prioritize getting max_gfn from GuestPhysBits
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.
Reported-by: Yi Lai <yi1.lai@intel.com>
Signed-off-by: Tao Su <tao1.su@linux.intel.com>
Tested-by: Yi Lai <yi1.lai@intel.com>
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
Link: https://lore.kernel.org/r/20240513014003.104593-1-tao1.su@linux.intel.com
[sean: tweak name, add comment and sanity check]
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'lib/ubsan.c')
0 files changed, 0 insertions, 0 deletions