RE: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-10 Thread Stuart Yoder
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

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-10 Thread Alex Williamson
On Thu, 2014-04-10 at 20:52 +, Stuart Yoder wrote: 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

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-10 Thread Alex Williamson
On Thu, 2014-04-10 at 15:15 -0600, Alex Williamson wrote: On Thu, 2014-04-10 at 20:52 +, Stuart Yoder wrote: 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

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-05 Thread Kim Phillips
Needed by platform device drivers, such as the vfio-platform driver [1], in order to bypass the existing OF, ACPI, id_table and name string matches, and successfully be able to be bound to any device, like so: echo vfio-platform /sys/bus/platform/devices/fff51000.ethernet/driver_override echo

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-02 Thread Kim Phillips
On Tue, 1 Apr 2014 17:23:24 -0700 Greg KH gre...@linuxfoundation.org wrote: On Tue, Apr 01, 2014 at 06:52:12PM -0500, Kim Phillips wrote: On Tue, 01 Apr 2014 10:28:54 -0600 Alex Williamson alex.william...@redhat.com wrote: The driver_override field allows us to specify the driver for a

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-02 Thread Alex Williamson
On Wed, 2014-04-02 at 17:06 -0500, Kim Phillips wrote: On Tue, 1 Apr 2014 17:23:24 -0700 Greg KH gre...@linuxfoundation.org wrote: On Tue, Apr 01, 2014 at 06:52:12PM -0500, Kim Phillips wrote: On Tue, 01 Apr 2014 10:28:54 -0600 Alex Williamson alex.william...@redhat.com wrote:

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-01 Thread Greg KH
On Tue, Apr 01, 2014 at 10:28:54AM -0600, Alex Williamson wrote: 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,

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-01 Thread Alex Williamson
On Tue, 2014-04-01 at 09:47 -0700, Greg KH wrote: On Tue, Apr 01, 2014 at 10:28:54AM -0600, Alex Williamson wrote: 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

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-01 Thread Kim Phillips
On Tue, 01 Apr 2014 10:28:54 -0600 Alex Williamson alex.william...@redhat.com wrote: 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

Re: [RFC PATCH] PCI: Introduce new device binding path using pci_dev.driver_override

2014-04-01 Thread Christoffer Dall
On Tue, Apr 01, 2014 at 11:15:40AM -0600, Alex Williamson wrote: On Tue, 2014-04-01 at 09:47 -0700, Greg KH wrote: On Tue, Apr 01, 2014 at 10:28:54AM -0600, Alex Williamson wrote: The driver_override field allows us to specify the driver for a device rather than relying on the driver to