diff options
author | Kevin Tian <kevin.tian@intel.com> | 2022-09-21 18:43:59 +0800 |
---|---|---|
committer | Alex Williamson <alex.williamson@redhat.com> | 2022-09-21 14:15:11 -0600 |
commit | ebb72b765fb49685c4603d2bff47a4ab5d2580a9 (patch) | |
tree | c46208cc3a3a717239cd16e6686d874744d06eea /MAINTAINERS | |
parent | ac1237912fbd0f2503344aa268ceb43628cdffa8 (diff) | |
download | linux-ebb72b765fb49685c4603d2bff47a4ab5d2580a9.tar.gz |
vfio/ccw: Use the new device life cycle helpers
ccw is the only exception which cannot use vfio_alloc_device() because its private device structure is designed to serve both mdev and parent. Life cycle of the parent is managed by css_driver so vfio_ccw_private must be allocated/freed in css_driver probe/remove path instead of conforming to vfio core life cycle for mdev. Given that use a wait/completion scheme so the mdev remove path waits after vfio_put_device() until receiving a completion notification from @release. The completion indicates that all active references on vfio_device have been released. After that point although free of vfio_ccw_private is delayed to css_driver it's at least guaranteed to have no parallel reference on released vfio device part from other code paths. memset() in @probe is removed. vfio_device is either already cleared when probed for the first time or cleared in @release from last probe. The right fix is to introduce separate structures for mdev and parent, but this won't happen in short term per prior discussions. Remove vfio_init/uninit_group_dev() as no user now. Suggested-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Reviewed-by: Eric Farman <farman@linux.ibm.com> Link: https://lore.kernel.org/r/20220921104401.38898-14-kevin.tian@intel.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions