Searched refs:mdevs_lock (Results 1 – 4 of 4) sorted by relevance
51 * 3. matrix_dev->mdevs_lock: required to access data stored in a matrix_mdev60 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_for_kvm() 70 * 1. matrix_dev->mdevs_lock78 mutex_unlock(&matrix_dev->mdevs_lock); in release_update_locks_for_kvm() 95 * 3. matrix_dev->mdevs_lock: required to access data stored in a matrix_mdev105 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_for_mdev() 116 * 1. matrix_dev->mdevs_lock125 mutex_unlock(&matrix_dev->mdevs_lock); in release_update_locks_for_mdev() 142 * 3. matrix_dev->mdevs_lock: required to access data stored in a matrix_mdev162 mutex_lock(&matrix_dev->mdevs_lock); in get_update_locks_by_apqn() [all...]
35 * @mdevs_lock: mutex for locking the AP matrix device. This lock will be51 struct mutex mdevs_lock; /* serializes access to each ap_matrix_mdev */ member
112 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.