diff options
author | Jason Gunthorpe <jgg@nvidia.com> | 2022-05-11 21:19:07 +0200 |
---|---|---|
committer | Alex Williamson <alex.williamson@redhat.com> | 2022-05-11 21:32:56 +0200 |
commit | ff806cbd90bd2cc3d08a026e26157e5b5a6b5e03 (patch) | |
tree | 7819b677d8ec507c30674fab9e3e1f35df74fd95 /lib/bitmap.c | |
parent | vfio/pci: Have all VFIO PCI drivers store the vfio_pci_core_device in drvdata (diff) | |
download | linux-ff806cbd90bd2cc3d08a026e26157e5b5a6b5e03.tar.xz linux-ff806cbd90bd2cc3d08a026e26157e5b5a6b5e03.zip |
vfio/pci: Remove vfio_device_get_from_dev()
The last user of this function is in PCI callbacks that want to convert
their struct pci_dev to a vfio_device. Instead of searching use the
vfio_device available trivially through the drvdata.
When a callback in the device_driver is called, the caller must hold the
device_lock() on dev. The purpose of the device_lock is to prevent
remove() from being called (see __device_release_driver), and allow the
driver to safely interact with its drvdata without races.
The PCI core correctly follows this and holds the device_lock() when
calling error_detected (see report_error_detected) and
sriov_configure (see sriov_numvfs_store).
Further, since the drvdata holds a positive refcount on the vfio_device
any access of the drvdata, under the device_lock(), from a driver callback
needs no further protection or refcounting.
Thus the remark in the vfio_device_get_from_dev() comment does not apply
here, VFIO PCI drivers all call vfio_unregister_group_dev() from their
remove callbacks under the device_lock() and cannot race with the
remaining callers.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/2-v4-c841817a0349+8f-vfio_get_from_dev_jgg@nvidia.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'lib/bitmap.c')
0 files changed, 0 insertions, 0 deletions