Xiong Zhang 9557588786 Devices: Allocate non pci bar mmio at top of HighMmio ... Some devices like virtio-pmem, intel host bridge need private mmio, these private mmio isn't exposed to Vm through pci bar, and crosvm use mmio allocation interface to allocate them, so guest OS pci bus driver couldn't detect them, and once guest OS reallocate pci mmio, these private mmmio could be assigned to pci device bar. then resource conflict happens. This patch allocates these non pci bar mmio at the top of HighMmio, since HighMmio is large enough and OS allocates pci mmio from low to high. So these non pci bar mmio won't conflict with pci bar. BUG=b:199442120 BUG=b:185084350 TEST=crosvm run --pmem-device xxxx Change-Id: I615d7901d595dd46ba6362f88b71d96baa9c4c8f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3184549 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>		2021-10-25 22:03:12 +00:00
..
src	Devices: Allocate non pci bar mmio at top of HighMmio	2021-10-25 22:03:12 +00:00
Cargo.toml	resources: convert to ThisError and sort	2021-09-24 21:13:19 +00:00