diff options
author | Juergen Gross <jgross@suse.com> | 2016-09-22 10:45:41 +0200 |
---|---|---|
committer | David Vrabel <david.vrabel@citrix.com> | 2016-09-30 11:49:02 +0100 |
commit | b057878b2aadc7e06280e7e702a36e7adb1bcdf7 (patch) | |
tree | ce12e3a3cdf29554fabd7b8418a68283396fa35b /Documentation/acpi/DSD-properties-rules.txt | |
parent | 9f8bee9c981f5fe7382a0615d117cc128dd22458 (diff) |
xen/pciback: support driver_override
Support the driver_override scheme introduced with commit 782a985d7af2
("PCI: Introduce new device binding path using pci_dev.driver_override")
As pcistub_probe() is called for all devices (it has to check for a
match based on the slot address rather than device type) it has to
check for driver_override set to "pciback" itself.
Up to now for assigning a pci device to pciback you need something like:
echo 0000:07:10.0 > /sys/bus/pci/devices/0000\:07\:10.0/driver/unbind
echo 0000:07:10.0 > /sys/bus/pci/drivers/pciback/new_slot
echo 0000:07:10.0 > /sys/bus/pci/drivers_probe
while with the patch you can use the same mechanism as for similar
drivers like pci-stub and vfio-pci:
echo pciback > /sys/bus/pci/devices/0000\:07\:10.0/driver_override
echo 0000:07:10.0 > /sys/bus/pci/devices/0000\:07\:10.0/driver/unbind
echo 0000:07:10.0 > /sys/bus/pci/drivers_probe
So e.g. libvirt doesn't need special handling for pciback.
Signed-off-by: Juergen Gross <jgross@suse.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'Documentation/acpi/DSD-properties-rules.txt')
0 files changed, 0 insertions, 0 deletions