Skip to content

vfio/mlx5: locking updates

Brett Creeley kvm lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2vfio/mlx5: Change reset_lock to mutex_lockdrivers/vfio/pci/mlx5/cmd.c drivers/vfio/pci/mlx5/cmd.h drivers/vfio/pci/mlx5/main.c+9 -90 replies
2/2vfio/mlx5: Destroy the state_mutex on releasedrivers/vfio/pci/mlx5/cmd.c+1 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH vfio 0/2] vfio/mlx5: locking updates

The vfio/pds series for locking updates/fixes in the following link made some changes that can also be done for other vendor's vfio drivers. Specifically, changing the reset lock from a spinlock to mutex and also calling mutex_destroy() in the vfio device release callback.

https://lore.kernel.org/kvm/[email protected]/

So, this series makes these changes in order to remain separate from the vfio/pds series linked above.

Note, that I don't have the required hardware to test on this vendor's hardware, so help would be appreciated.

Brett Creeley (2):
vfio/mlx5: Change reset_lock to mutex_lock
vfio/mlx5: Destroy the state_mutex on release

 drivers/vfio/pci/mlx5/cmd.c  |  4 +++-
 drivers/vfio/pci/mlx5/cmd.h  |  3 +--
 drivers/vfio/pci/mlx5/main.c | 12 ++++++------
 3 files changed, 10 insertions(+), 9 deletions(-)
Signature · 1 line
2.17.1