David Stevens dbd241847b system_allocator: add mmio-address-range parameter ... Linux expects that PCI bars lie within a compatible bridge window, which are typically specified via _CRS objects in ACPI. This change adds an option to restrict mmio allocations (i.e. PCI bars) to within a specified set of ranges. The specified set of ranges is intersected with the default mmio allocation ranges generated by the crosvm arch code to produce the final mmio allocation ranges. This change is required to remove pci=nocrs from the CrOS guest's kernel command line flags. Removing that flag is a prerequisite for enabling virtio-iommu, since without the configuration information from ACPI, the kernel reserves all IOVAs in iova_reserve_pci_windows. BUG=b:181736020 TEST=boot manatee w/o pci=nocrs kernel cmdline flag TEST=tast run trogdor|hatch arc.Boot.vm Change-Id: I0a096420c5d5ef56dd76021951968e264ce40f42 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3499900 Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: David Stevens <stevensd@chromium.org>		2022-03-17 01:58:15 +00:00
..
kvm	system_allocator: add mmio-address-range parameter	2022-03-17 01:58:15 +00:00
aarch64.rs
ioapic.rs	irqchip: ioapic: Introduce 1:1 GSI mapping for direct IRQ forwarding	2022-03-11 11:14:01 +00:00
mod.rs	irqchip: kvm: Fix IOAPIC delayed IRQs	2022-03-16 18:58:54 +00:00
pic.rs	clippy: fix devices crate	2022-02-07 22:22:39 +00:00
x86_64.rs