From: "Jason J. Herne" <jjherne@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: freude@linux.ibm.com, borntraeger@de.ibm.com, cohuck@redhat.com,
mjrosato@linux.ibm.com, pasic@linux.ibm.com,
alex.williamson@redhat.com, kwankhede@nvidia.com,
fiuczy@linux.ibm.com
Subject: Re: [PATCH v20 10/20] s390/vfio-ap: prepare for dynamic update of guest's APCB on assign/unassign
Date: Tue, 21 Jun 2022 16:02:23 -0400 [thread overview]
Message-ID: <99ddfadd-7aac-8f3c-9f07-ae2b66cf45cc@linux.ibm.com> (raw)
In-Reply-To: <20220621155134.1932383-11-akrowiak@linux.ibm.com>
On 6/21/22 11:51, Tony Krowiak wrote:
> The functions backing the matrix mdev's sysfs attribute interfaces to
> assign/unassign adapters, domains and control domains must take and
> release the locks required to perform a dynamic update of a guest's APCB
> in the proper order.
>
> The proper order for taking the locks is:
>
> matrix_dev->guests_lock => kvm->lock => matrix_dev->mdevs_lock
>
> The proper order for releasing the locks is:
>
> matrix_dev->mdevs_lock => kvm->lock => matrix_dev->guests_lock
>
> Two new macros are introduced for this purpose: One to take the locks and
> the other to release the locks. These macros will be used by the
> assignment/unassignment functions to prepare for dynamic update of
> the KVM guest's APCB.
>
> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 69 +++++++++++++++++++++++++------
> 1 file changed, 57 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
> index f31db1248740..b8f901e6b580 100644
> --- a/drivers/s390/crypto/vfio_ap_ops.c
> +++ b/drivers/s390/crypto/vfio_ap_ops.c
> @@ -75,6 +75,51 @@ static const struct vfio_device_ops vfio_ap_matrix_dev_ops;
> mutex_unlock(&matrix_dev->guests_lock); \
> })
>
> +/**
> + * get_update_locks_for_mdev: Acquire the locks required to dynamically update a
> + * KVM guest's APCB in the proper order.
> + *
> + * @matrix_mdev: a pointer to a struct ap_matrix_mdev object containing the AP
> + * configuration data to use to update a KVM guest's APCB.
> + *
> + * The proper locking order is:
> + * 1. matrix_dev->guests_lock: required to use the KVM pointer to update a KVM
> + * guest's APCB.
> + * 2. matrix_mdev->kvm->lock: required to update a guest's APCB
> + * 3. matrix_dev->mdevs_lock: required to access data stored in a matrix_mdev
> + *
> + * Note: If @matrix_mdev is NULL or is not attached to a KVM guest, the KVM
> + * lock will not be taken.
> + */
> +#define get_update_locks_for_mdev(matrix_mdev) ({ \
> + mutex_lock(&matrix_dev->guests_lock); \
> + if (matrix_mdev && matrix_mdev->kvm) \
> + mutex_lock(&matrix_mdev->kvm->lock); \
> + mutex_lock(&matrix_dev->mdevs_lock); \
> +})
> +
> +/**
> + * release_update_locks_for_mdev: Release the locks used to dynamically update a
> + * KVM guest's APCB in the proper order.
> + *
> + * @matrix_mdev: a pointer to a struct ap_matrix_mdev object containing the AP
> + * configuration data to use to update a KVM guest's APCB.
> + *
> + * The proper unlocking order is:
> + * 1. matrix_dev->mdevs_lock
> + * 2. matrix_mdev->kvm->lock
> + * 3. matrix_dev->guests_lock
> + *
> + * Note: If @matrix_mdev is NULL or is not attached to a KVM guest, the KVM
> + * lock will not be released.
> + */
> +#define release_update_locks_for_mdev(matrix_mdev) ({ \
> + mutex_unlock(&matrix_dev->mdevs_lock); \
> + if (matrix_mdev && matrix_mdev->kvm) \
> + mutex_unlock(&matrix_mdev->kvm->lock); \
> + mutex_unlock(&matrix_dev->guests_lock); \
> +})
> +
> /**
> * vfio_ap_mdev_get_queue - retrieve a queue with a specific APQN from a
> * hash table of queues assigned to a matrix mdev
> @@ -830,7 +875,7 @@ static ssize_t assign_adapter_store(struct device *dev,
>
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If the KVM guest is running, disallow assignment of adapter */
> if (matrix_mdev->kvm) {
> @@ -862,7 +907,7 @@ static ssize_t assign_adapter_store(struct device *dev,
> matrix_mdev->matrix.aqm, matrix_mdev);
> ret = count;
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
>
> return ret;
> }
> @@ -905,7 +950,7 @@ static ssize_t unassign_adapter_store(struct device *dev,
> unsigned long apid;
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If the KVM guest is running, disallow unassignment of adapter */
> if (matrix_mdev->kvm) {
> @@ -930,7 +975,7 @@ static ssize_t unassign_adapter_store(struct device *dev,
>
> ret = count;
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
> return ret;
> }
> static DEVICE_ATTR_WO(unassign_adapter);
> @@ -985,7 +1030,7 @@ static ssize_t assign_domain_store(struct device *dev,
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
> unsigned long max_apqi = matrix_mdev->matrix.aqm_max;
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If the KVM guest is running, disallow assignment of domain */
> if (matrix_mdev->kvm) {
> @@ -1016,7 +1061,7 @@ static ssize_t assign_domain_store(struct device *dev,
> matrix_mdev);
> ret = count;
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
>
> return ret;
> }
> @@ -1059,7 +1104,7 @@ static ssize_t unassign_domain_store(struct device *dev,
> unsigned long apqi;
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If the KVM guest is running, disallow unassignment of domain */
> if (matrix_mdev->kvm) {
> @@ -1085,7 +1130,7 @@ static ssize_t unassign_domain_store(struct device *dev,
> ret = count;
>
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
> return ret;
> }
> static DEVICE_ATTR_WO(unassign_domain);
> @@ -1112,7 +1157,7 @@ static ssize_t assign_control_domain_store(struct device *dev,
> unsigned long id;
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If the KVM guest is running, disallow assignment of control domain */
> if (matrix_mdev->kvm) {
> @@ -1138,7 +1183,7 @@ static ssize_t assign_control_domain_store(struct device *dev,
> vfio_ap_mdev_filter_cdoms(matrix_mdev);
> ret = count;
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
> return ret;
> }
> static DEVICE_ATTR_WO(assign_control_domain);
> @@ -1166,7 +1211,7 @@ static ssize_t unassign_control_domain_store(struct device *dev,
> struct ap_matrix_mdev *matrix_mdev = dev_get_drvdata(dev);
> unsigned long max_domid = matrix_mdev->matrix.adm_max;
>
> - mutex_lock(&matrix_dev->mdevs_lock);
> + get_update_locks_for_mdev(matrix_mdev);
>
> /* If a KVM guest is running, disallow unassignment of control domain */
> if (matrix_mdev->kvm) {
> @@ -1189,7 +1234,7 @@ static ssize_t unassign_control_domain_store(struct device *dev,
>
> ret = count;
> done:
> - mutex_unlock(&matrix_dev->mdevs_lock);
> + release_update_locks_for_mdev(matrix_mdev);
> return ret;
> }
> static DEVICE_ATTR_WO(unassign_control_domain);
Reviewed-by: Jason J. Herne <jjherne@linux.ibm.com>
--
-- Jason J. Herne (jjherne@linux.ibm.com)
next prev parent reply other threads:[~2022-06-21 20:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 15:51 [PATCH v20 00/20] s390/vfio-ap: dynamic configuration support Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 01/20] s390/vfio-ap: use new AP bus interface to search for queue devices Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 02/20] s390/vfio-ap: move probe and remove callbacks to vfio_ap_ops.c Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 03/20] s390/vfio-ap: manage link between queue struct and matrix mdev Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 04/20] s390/vfio-ap: introduce shadow APCB Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 05/20] s390/vfio-ap: refresh guest's APCB by filtering AP resources assigned to mdev Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 06/20] s390/vfio-ap: allow assignment of unavailable AP queues to mdev device Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 07/20] s390/vfio-ap: rename matrix_dev->lock mutex to matrix_dev->mdevs_lock Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 08/20] s390/vfio-ap: introduce new mutex to control access to the KVM pointer Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 09/20] s390/vfio-ap: use proper locking order when setting/clearing " Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 10/20] s390/vfio-ap: prepare for dynamic update of guest's APCB on assign/unassign Tony Krowiak
2022-06-21 20:02 ` Jason J. Herne [this message]
2022-06-21 15:51 ` [PATCH v20 11/20] s390/vfio-ap: prepare for dynamic update of guest's APCB on queue probe/remove Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 12/20] s390/vfio-ap: allow hot plug/unplug of AP devices when assigned/unassigned Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 13/20] s390/vfio-ap: hot plug/unplug of AP devices when probed/removed Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 14/20] s390/vfio-ap: reset queues after adapter/domain unassignment Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 15/20] s390/vfio-ap: implement in-use callback for vfio_ap driver Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 16/20] s390/vfio-ap: sysfs attribute to display the guest's matrix Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 17/20] s390/vfio-ap: handle config changed and scan complete notification Tony Krowiak
2022-06-21 15:51 ` [PATCH v20 18/20] s390/vfio-ap: update docs to include dynamic config support Tony Krowiak
2022-07-04 21:20 ` kernel test robot
2022-06-21 15:51 ` [PATCH v20 19/20] s390/Docs: new doc describing lock usage by the vfio_ap device driver Tony Krowiak
2022-07-05 4:59 ` kernel test robot
2022-07-05 7:46 ` kernel test robot
2022-06-21 15:51 ` [PATCH v20 20/20] MAINTAINERS: pick up all vfio_ap docs for VFIO AP maintainers Tony Krowiak
2022-06-21 19:56 ` Jason J. Herne
2022-06-22 6:48 ` [PATCH v20 00/20] s390/vfio-ap: dynamic configuration support Christian Borntraeger
2022-06-22 10:42 ` Halil Pasic
2022-06-22 12:40 ` Tony Krowiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99ddfadd-7aac-8f3c-9f07-ae2b66cf45cc@linux.ibm.com \
--to=jjherne@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=fiuczy@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox