search for: _vdpa_unregister_device

...->nb_registered = false; > mlx5_notifier_unregister(mvdev->mdev, &ndev->nb); > @@ -3332,6 +3330,8 @@ static void mlx5_vdpa_dev_del(struct vdpa_mgmt_dev *v_mdev, struct vdpa_device * > mvdev->wq = NULL; > destroy_workqueue(wq); > _vdpa_unregister_device(dev); What if the user tries to access debugfs after _vdpa_unregister_device()? Thanks > + mlx5_vdpa_remove_debugfs(ndev->debugfs); > + ndev->debugfs = NULL; > mgtdev->ndev = NULL; > } > > -- > 2.38.1 >

Live migration of vdpa would typically require re-instate vdpa device with an idential set of configs on the destination node, same way as how source node created the device in the first place. In order to allow live migration orchestration software to export the initial set of vdpa attributes with which the device was created, it will be useful if the vdpa tool can report the config on demand