Jason Wang 1c80cf031e vdpa: mlx5: synchronize driver status with CVQ ... Currently, CVQ doesn't have any synchronization with the driver status. Then CVQ emulation code run in the middle of: 1) device reset 2) device status changed 3) map updating The will lead several unexpected issue like trying to execute CVQ command after the driver has been teared down. Fixing this by using reslock to synchronize CVQ emulation code with the driver status changing: - protect the whole device reset, status changing and set_map() updating with reslock - protect the CVQ handler with the reslock and check VIRTIO_CONFIG_S_DRIVER_OK in the CVQ handler This will guarantee that: 1) CVQ handler won't work if VIRTIO_CONFIG_S_DRIVER_OK is not set 2) CVQ handler will see a consistent state of the driver instead of the partial one when it is running in the middle of the teardown_driver() or setup_driver(). Cc: 5262912ef3 ("vdpa/mlx5: Add support for control VQ and MAC setting") Signed-off-by: Jason Wang <jasowang@redhat.com> Link: https://lore.kernel.org/r/20220329042109.4029-2-jasowang@redhat.com Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Acked-by: Eli Cohen <elic@nvidia.com>		2022-03-30 04:18:14 -04:00
..
core	vhost,virtio,vhost: fixes,features	2021-11-03 15:00:39 -07:00
net	vdpa: mlx5: synchronize driver status with CVQ	2022-03-30 04:18:14 -04:00
Makefile	vdpa/mlx5: Connect mlx5_vdpa to auxiliary bus	2020-12-06 07:32:05 +02:00