On Mon, 2012-06-04 at 17:29 -0400, Donald Dutile wrote: > Intel-iommu initialization doesn't currently reserve the memory used > for the IOMMU registers. This can allow the pci resource allocator > to assign a device BAR to the same address as the IOMMU registers. > This can cause some not so nice side affects when the driver > ioremap's that region.
s/affect/effect/ And surely this can happen even when IOMMU support is compiled out of the kernel. Shouldn't the BIOS be *telling* us that this region is unavailable for PCI resource allocation (or anything else, for that matter)? If the BIOS *doesn't* do that, then I believe this should be WARN_TAINT_ONCE(…TAINT_FIRMWARE_WORKAROUND…) like other BIOS problems that we have discovered. And we should probably do it based on the actual chipset registers, not the DMAR tables (which the BIOS has also been known to lie about). -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
