diff options
| author | Igor Druzhinin <igor.druzhinin@citrix.com> | 2019-04-25 21:23:56 +0100 |
|---|---|---|
| committer | Laszlo Ersek <lersek@redhat.com> | 2019-04-30 18:41:57 +0200 |
| commit | 27e4d6ae25a08a6e9d78b27ce201800d3d072401 (patch) | |
| tree | fa632032c7bcf850f8c4ef02d05bf0e8eaba32d4 /BaseTools/Source/Python/Ecc/FileProfile.py | |
| parent | 9fb2ce2f465d555f70c2ab9365a11e031d0049c4 (diff) | |
| download | edk2-27e4d6ae25a08a6e9d78b27ce201800d3d072401.tar.gz edk2-27e4d6ae25a08a6e9d78b27ce201800d3d072401.tar.bz2 edk2-27e4d6ae25a08a6e9d78b27ce201800d3d072401.zip | |
OvmfPkg/XenSupport: remove usage of prefetchable PCI host bridge aperture
This aperture doesn't exist in QEMU-XEN and hvmloader places BARs
in arbitrary order disregarding prefetchable bit. This makes
prefetchable and non-prefetchable BARs to follow each other that's
quite likely with PCI passthrough devices. In that case, the existing
code, that tries to work out aperture boundaries by reading hvmloader
BAR placement, will report a bogus prefetchable aperture which overlaps
with the regular one. It will eventually trigger an assertion in
DXE PCI initialization code.
Do the same thing as OVMF on QEMU-KVM and pass a non-existing aperture
there. It's not necessary to pass additional allocation flags as we set
ResourceAssigned flag on the root bridge which means they will be ignored.
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
Diffstat (limited to 'BaseTools/Source/Python/Ecc/FileProfile.py')
0 files changed, 0 insertions, 0 deletions