aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/pci/pci-driver.c
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2014-05-20 10:53:21 -0400
committerBjorn Helgaas <bhelgaas@google.com>2014-05-28 18:04:53 -0400
commit782a985d7af26db39e86070d28f987cad21313c0 (patch)
tree637034dde8f75f513c4fdde6450773c4adc96e8f /drivers/pci/pci-driver.c
parent3cb30b73ad71b384c6289243d4ccd31ab90bce6f (diff)
PCI: Introduce new device binding path using pci_dev.driver_override
The driver_override field allows us to specify the driver for a device rather than relying on the driver to provide a positive match of the device. This shortcuts the existing process of looking up the vendor and device ID, adding them to the driver new_id, binding the device, then removing the ID, but it also provides a couple advantages. First, the above existing process allows the driver to bind to any device matching the new_id for the window where it's enabled. This is often not desired, such as the case of trying to bind a single device to a meta driver like pci-stub or vfio-pci. Using driver_override we can do this deterministically using: echo pci-stub > /sys/bus/pci/devices/0000:03:00.0/driver_override echo 0000:03:00.0 > /sys/bus/pci/devices/0000:03:00.0/driver/unbind echo 0000:03:00.0 > /sys/bus/pci/drivers_probe Previously we could not invoke drivers_probe after adding a device to new_id for a driver as we get non-deterministic behavior whether the driver we intend or the standard driver will claim the device. Now it becomes a deterministic process, only the driver matching driver_override will probe the device. To return the device to the standard driver, we simply clear the driver_override and reprobe the device: echo > /sys/bus/pci/devices/0000:03:00.0/driver_override echo 0000:03:00.0 > /sys/bus/pci/devices/0000:03:00.0/driver/unbind echo 0000:03:00.0 > /sys/bus/pci/drivers_probe Another advantage to this approach is that we can specify a driver override to force a specific binding or prevent any binding. For instance when an IOMMU group is exposed to userspace through VFIO we require that all devices within that group are owned by VFIO. However, devices can be hot-added into an IOMMU group, in which case we want to prevent the device from binding to any driver (override driver = "none") or perhaps have it automatically bind to vfio-pci. With driver_override it's a simple matter for this field to be set internally when the device is first discovered to prevent driver matches. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Reviewed-by: Alexander Graf <agraf@suse.de> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/pci/pci-driver.c')
-rw-r--r--drivers/pci/pci-driver.c25
1 files changed, 22 insertions, 3 deletions
diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
index d911e0c1f359..4393c12e9135 100644
--- a/drivers/pci/pci-driver.c
+++ b/drivers/pci/pci-driver.c
@@ -216,6 +216,13 @@ const struct pci_device_id *pci_match_id(const struct pci_device_id *ids,
216 return NULL; 216 return NULL;
217} 217}
218 218
219static const struct pci_device_id pci_device_id_any = {
220 .vendor = PCI_ANY_ID,
221 .device = PCI_ANY_ID,
222 .subvendor = PCI_ANY_ID,
223 .subdevice = PCI_ANY_ID,
224};
225
219/** 226/**
220 * pci_match_device - Tell if a PCI device structure has a matching PCI device id structure 227 * pci_match_device - Tell if a PCI device structure has a matching PCI device id structure
221 * @drv: the PCI driver to match against 228 * @drv: the PCI driver to match against
@@ -229,18 +236,30 @@ static const struct pci_device_id *pci_match_device(struct pci_driver *drv,
229 struct pci_dev *dev) 236 struct pci_dev *dev)
230{ 237{
231 struct pci_dynid *dynid; 238 struct pci_dynid *dynid;
239 const struct pci_device_id *found_id = NULL;
240
241 /* When driver_override is set, only bind to the matching driver */
242 if (dev->driver_override && strcmp(dev->driver_override, drv->name))
243 return NULL;
232 244
233 /* Look at the dynamic ids first, before the static ones */ 245 /* Look at the dynamic ids first, before the static ones */
234 spin_lock(&drv->dynids.lock); 246 spin_lock(&drv->dynids.lock);
235 list_for_each_entry(dynid, &drv->dynids.list, node) { 247 list_for_each_entry(dynid, &drv->dynids.list, node) {
236 if (pci_match_one_device(&dynid->id, dev)) { 248 if (pci_match_one_device(&dynid->id, dev)) {
237 spin_unlock(&drv->dynids.lock); 249 found_id = &dynid->id;
238 return &dynid->id; 250 break;
239 } 251 }
240 } 252 }
241 spin_unlock(&drv->dynids.lock); 253 spin_unlock(&drv->dynids.lock);
242 254
243 return pci_match_id(drv->id_table, dev); 255 if (!found_id)
256 found_id = pci_match_id(drv->id_table, dev);
257
258 /* driver_override will always match, send a dummy id */
259 if (!found_id && dev->driver_override)
260 found_id = &pci_device_id_any;
261
262 return found_id;
244} 263}
245 264
246struct drv_dev_and_id { 265struct drv_dev_and_id {