Daniel Verkamp 82e7bfedaa x86_64: fix off by one of high MMIO range end ... The code was unintentionally subtracting 1 (to get the inclusive end address) twice, leaving off one extra byte. This doesn't make much difference in practice since the high MMIO region is typically very large (up to 64 terabytes). The result can be observed in the guest's /proc/iomem, where the PCI region should now end at 0x..ffff instead of 0x...fffe. BUG=None TEST=Boot x86-64 Linux kernel; cat /proc/iomem Change-Id: I2df210ed40612cefce68926c616f455e416ed40c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3790030 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Daniel Verkamp <dverkamp@chromium.org>		2022-08-02 01:07:04 +00:00
..
src	x86_64: fix off by one of high MMIO range end	2022-08-02 01:07:04 +00:00
Cargo.toml	x86_64: build and test on windows	2022-07-19 23:55:49 +00:00