Rob Bradford 180e6d1e78 vm-virtio: Allocate BARs for virtio-block devices in 32-bit hole ... Currently all devices and guest memory share the same 64GiB allocation. With guest memory working upwards and devices working downwards. This creates issues if you want to either have a VM with a large amount of memory or want to have devices with a large allocation (e.g. virtio-pmem.) As it is possible for the hypervisor to place devices anywhere in its address range it is required for simplistic users like the firmware to set up an identity page table mapping across the full range. Currently the hypervisor sets up an identify mapping of 1GiB which the firmware extends to 64GiB to match the current address space size of the hypervisor. A simpler solution is to place the device needed for booting with the firmware (virtio-block) inside the 32-bit memory hole. This allows the firmware to easily access the block device and paves the way for increasing the address space beyond the current 64GiB limit. Signed-off-by: Rob Bradford <robert.bradford@intel.com>		2019-09-19 10:43:55 +01:00
..
src	vm-virtio: Allocate BARs for virtio-block devices in 32-bit hole	2019-09-19 10:43:55 +01:00
Cargo.toml	vm-virtio: Add MMIO transport	2019-09-13 12:30:13 +01:00