aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/s390/cio/vfio_ccw_ops.c
diff options
context:
space:
mode:
authorCornelia Huck <cohuck@redhat.com>2019-06-13 13:08:15 +0200
committerVasily Gorbik <gor@linux.ibm.com>2019-07-02 16:00:26 +0200
commitebc3d179150347f3b6d97d8f249378bb2218f95e (patch)
treefd608926e7c655a331816d91722b45ef4cec11e5 /drivers/s390/cio/vfio_ccw_ops.c
parentvfio-ccw: make convert_ccw0_to_ccw1 static (diff)
downloadlinux-dev-ebc3d179150347f3b6d97d8f249378bb2218f95e.tar.xz
linux-dev-ebc3d179150347f3b6d97d8f249378bb2218f95e.zip
s390/cio: introduce driver_override on the css bus
Sometimes, we want to control which of the matching drivers binds to a subchannel device (e.g. for subchannels we want to handle via vfio-ccw). For pci devices, a mechanism to do so has been introduced in 782a985d7af2 ("PCI: Introduce new device binding path using pci_dev.driver_override"). It makes sense to introduce the driver_override attribute for subchannel devices as well, so that we can easily extend the 'driverctl' tool (which makes use of the driver_override attribute for pci). Note that unlike pci we still require a driver override to match the subchannel type; matching more than one subchannel type is probably not useful anyway. Signed-off-by: Cornelia Huck <cohuck@redhat.com> Reviewed-by: Halil Pasic <pasic@linux.ibm.com> Reviewed-by: Sebastian Ott <sebott@linux.ibm.com> Signed-off-by: Sebastian Ott <sebott@linux.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'drivers/s390/cio/vfio_ccw_ops.c')
0 files changed, 0 insertions, 0 deletions