Searched refs:matrix_dev (Results 1 – 2 of 2) sorted by relevance
26 struct ap_matrix_dev *matrix_dev; variable39 ATTRIBUTE_GROUPS(matrix_dev);69 struct ap_matrix_dev *matrix_dev; in vfio_ap_matrix_dev_release() local71 matrix_dev = container_of(dev, struct ap_matrix_dev, device); in vfio_ap_matrix_dev_release()72 kfree(matrix_dev); in vfio_ap_matrix_dev_release()99 matrix_dev = kzalloc_obj(*matrix_dev); in vfio_ap_matrix_dev_create()100 if (!matrix_dev) { in vfio_ap_matrix_dev_create()107 ret = ap_qci(&matrix_dev->info); in vfio_ap_matrix_dev_create()112 mutex_init(&matrix_dev->mdevs_lock); in vfio_ap_matrix_dev_create()113 INIT_LIST_HEAD(&matrix_dev->mdev_list); in vfio_ap_matrix_dev_create()[all …]
12 struct ap_matrix_dev *matrix_dev;28 The Matrix Devices Lock (matrix_dev->mdevs_lock) is implemented as a global31 (matrix_dev->mdev_list). This lock must be held while reading from, writing to66 The Guests Lock (matrix_dev->guests_lock) controls access to the67 matrix_mdev instances (matrix_dev->mdev_list) that represent mediated devices75 2. To add matrix_mdev instances to or remove them from matrix_dev->mdev_list.90 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.