VT-d: Fix PCI-X device assignment
authorKeir Fraser <keir.fraser@citrix.com>
Fri, 19 Dec 2008 13:42:04 +0000 (13:42 +0000)
committerKeir Fraser <keir.fraser@citrix.com>
Fri, 19 Dec 2008 13:42:04 +0000 (13:42 +0000)
commit8c13de56874c22fe863eaea97502095805e4cdb6
tree1fe68b21cbad9f0a20f989e1318e6a2e0e1a7e54
parent1e5e52220face08873ad8e2b3e04b8260c5661a9
VT-d: Fix PCI-X device assignment

When assign PCI device, current code just map its bridge and its
secondary bus number and devfn 0. It doesn't work for PCI-x device
assignment, because the request may be the source-id in the original
PCI-X transaction or the source-id provided by the bridge. It needs to
map the device itself, and its upstream bridges till PCIe-to-PCI/PCI-x
bridge.

In addition, add description for DEV_TYPE_PCIe_BRIDGE and
DEV_TYPE_PCI_BRIDGE for understandability.

Signed-off-by: Weidong Han <weidong.han@intel.com>
xen/drivers/passthrough/vtd/iommu.c