Searched refs:mdevs_lock (Results 1 – 4 of 4) sorted by relevance
57 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_for_kvm()75 mutex_unlock(&matrix_dev->mdevs_lock); in release_update_locks_for_kvm()102 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_for_mdev()122 mutex_unlock(&matrix_dev->mdevs_lock); in release_update_locks_for_mdev()159 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_by_apqn()165 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_by_apqn()191 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_for_queue()550 mutex_lock(&matrix_dev->mdevs_lock); in handle_pqap()590 mutex_unlock(&matrix_dev->mdevs_lock); in handle_pqap()715 mutex_lock(&matrix_dev->mdevs_lock); in vfio_ap_mdev_probe()[all …]
50 struct mutex mdevs_lock; /* serializes access to each ap_matrix_mdev */ member
104 mutex_init(&matrix_dev->mdevs_lock); in vfio_ap_matrix_dev_create()
24 struct mutex mdevs_lock;28 The Matrix Devices Lock (matrix_dev->mdevs_lock) is implemented as a global90 however, in this case, the Matrix Devices Lock (matrix_dev->mdevs_lock) must be95 resources, so only the matrix_dev->mdevs_lock needs to be held.