vt-d: Only setup rmrr identity mappings of the assigned devices

Current implementation setups identity mappings for all the rmrrs
whether the assigned device has rmrr or not. It's wasteful and not
necessary, because only USB controllers and UMA integarated graphics
devices have rmrr. This patch only setups rmrr identity mappings of
the assigned devices. If the assigned devices don't have rmrr, needn't
to setup rmrr identity mapping for guest.

BTW, this patch fixes the VT-d bug (Fail to boot smp Linux guest with
VT-d NIC assigned on IA32e platform).

Signed-off-by: Weidong Han <weidong.han@intel.com>
This commit is contained in:
Keir Fraser committed 2007-12-28 15:26:27 +00:00
1 parent 8f8a3b5659
commit e6bf9545fd
1 file changed
+10 -7
+10 -7
View File
@@ -1866,14 +1866,17 @@ int assign_device(struct domain *d, u8 bus, u8 devfn)
reassign_device_ownership(dom0, d, bus, devfn);
/* setup rmrr identify mapping just once per domain */
for_each_rmrr_device(rmrr, pdev)
ret = iommu_prepare_rmrr_dev(d, rmrr, pdev);
if ( ret )
/* Setup rmrr identify mapping */
for_each_rmrr_device( rmrr, pdev )
if ( pdev->bus == bus && pdev->devfn == devfn )
{
gdprintk(XENLOG_ERR VTDPREFIX,
"IOMMU: mapping reserved region failed\n");
return ret;
ret = iommu_prepare_rmrr_dev(d, rmrr, pdev);
if ( ret )
{
gdprintk(XENLOG_ERR VTDPREFIX,
"IOMMU: mapping reserved region failed\n");
return ret;
}
}
end_for_each_rmrr_device(rmrr, pdev)
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.