Lines Matching +full:sub +full:- +full:domains

1 .. SPDX-License-Identifier: GPL-2.0
10 .. code-block:: c
17 ---------------------------------------------------------------
19 .. code-block:: c
28 The Matrix Devices Lock (matrix_dev->mdevs_lock) is implemented as a global
31 (matrix_dev->mdev_list). This lock must be held while reading from, writing to
36 ---------------------------------------
38 .. code-block:: c
46 The KVM Lock (kvm->lock) controls access to the state data for a KVM guest. This
48 domains or control domains are being plugged into or unplugged from the guest.
51 (matrix_mdev->kvm = kvm) containing the state of the mediated device that has
55 -----------------------------------------------------------
57 .. code-block:: c
66 The Guests Lock (matrix_dev->guests_lock) controls access to the
67 matrix_mdev instances (matrix_dev->mdev_list) that represent mediated devices
71 1. To control access to the KVM pointer (matrix_mdev->kvm) while the vfio_ap
75 2. To add matrix_mdev instances to or remove them from matrix_dev->mdev_list.
84    found. The KVM pointer (matrix_mdev->kvm) can then be used to determine if
85    the mediated device is passed through (matrix_mdev->kvm != NULL) and if so,
90 however, in this case, the Matrix Devices Lock (matrix_dev->mdevs_lock) must be
93 handles interception of the PQAP(AQIC) instruction sub-function. This handler
95 resources, so only the matrix_dev->mdevs_lock needs to be held.
98 -----------------------------------------------------
100 .. code-block:: c
112 pointer of the handler ``(*kvm->arch.crypto.pqap_hook)`` to invoke when the
113 PQAP(AQIC) instruction sub-function is intercepted by the host. The lock must be