Lines Matching refs:devices

4 to help ensure I/O devices behave within the boundaries they've been
45 meant for translation (ie. solving the addressing problems of devices
46 with limited address spaces).  With this, devices can now be isolated
48 things like secure direct assignment of devices into virtual machines.
51 though.  Even when an IOMMU is capable of this, properties of devices,
55 between devices within the enclosure, the enclosure may not require
56 transactions between devices to reach the IOMMU.  Examples of this
60 can also play a factor in terms of hiding devices.  A PCIe-to-PCI
61 bridge masks the devices behind it, making transaction appear as if
68 a set of devices which is isolatable from all other devices in the
90 If the IOMMU group contains multiple devices, each will need to
121 $ readlink /sys/bus/pci/devices/0000:06:0d.0/iommu_group
131 character devices for this group:
135 # echo 0000:06:0d.0 > /sys/bus/pci/devices/0000:06:0d.0/driver/unbind
138 Now we need to look at what other devices are in the group to free
141 $ ls -l /sys/bus/pci/devices/0000:06:0d.0/iommu_group/devices
144 	../../../../devices/pci0000:00/0000:00:1e.0
146 	../../../../devices/pci0000:00/0000:00:1e.0/0000:06:0d.0
148 	../../../../devices/pci0000:00/0000:00:1e.0/0000:06:0d.1
164 The user now has full access to all the devices and the iommu for this
190 		/* Group is not viable (ie, not all devices bound for vfio) */
224 		 * For PCI devices, config space is a region */
249 into VFIO core.  When devices are bound and unbound to the driver,
376 	 * PE, and put child devices belonging to same IOMMU group to the
493 possible for multi-function devices to have backdoors between
494 functions and even for single function devices to have alternative
497 IOMMU driver to group multi-function PCI devices together