From: Cornelia Huck <cohuck@redhat.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, freude@linux.ibm.com,
borntraeger@de.ibm.com, mjrosato@linux.ibm.com,
pmorel@linux.ibm.com, pasic@linux.ibm.com,
alex.williamson@redhat.com, kwankhede@nvidia.com,
jjherne@linux.ibm.com, fiuczy@linux.ibm.com
Subject: Re: [PATCH v7 02/15] s390/vfio-ap: manage link between queue struct and matrix mdev
Date: Thu, 9 Apr 2020 17:06:02 +0200 [thread overview]
Message-ID: <20200409170602.4440be0f.cohuck@redhat.com> (raw)
In-Reply-To: <20200407192015.19887-3-akrowiak@linux.ibm.com>
On Tue, 7 Apr 2020 15:20:02 -0400
Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> A vfio_ap_queue structure is created for each queue device probed. To
> ensure that the matrix mdev to which a queue's APQN is assigned is linked
> to the queue structure as long as the queue device is bound to the vfio_ap
> device driver, let's go ahead and manage these links when the queue device
> is probed and removed as well as whenever an adapter or domain is assigned
> to or unassigned from the matrix mdev.
>
> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 75 ++++++++++++++++++++++++++++---
> 1 file changed, 70 insertions(+), 5 deletions(-)
(...)
> @@ -536,6 +531,31 @@ static int vfio_ap_mdev_verify_no_sharing(struct ap_matrix_mdev *matrix_mdev)
> return 0;
> }
>
> +/**
> + * vfio_ap_mdev_qlinks_for_apid
Hm... maybe the function name should express that there's some actual
(un)linking going on?
vfio_ap_mdev_link_by_apid?
Or make this vfio_ap_mdev_link_queues() and pass in an indicator whether
the passed value is an apid or an aqid? Both function names look so
very similar to be easily confused (at least to me).
> + *
> + * @matrix_mdev: a matrix mediated device
> + * @apqi: the APID of one or more APQNs assigned to @matrix_mdev
> + *
> + * Set the link to @matrix_mdev for each queue device bound to the vfio_ap
> + * device driver with an APQN assigned to @matrix_mdev with the specified @apid.
> + *
> + * Note: If @matrix_mdev is NULL, the link to @matrix_mdev will be severed.
> + */
> +static void vfio_ap_mdev_qlinks_for_apid(struct ap_matrix_mdev *matrix_mdev,
> + unsigned long apid)
> +{
> + unsigned long apqi;
> + struct vfio_ap_queue *q;
> +
> + for_each_set_bit_inv(apqi, matrix_mdev->matrix.aqm,
> + matrix_mdev->matrix.aqm_max + 1) {
> + q = vfio_ap_get_queue(AP_MKQID(apid, apqi));
> + if (q)
> + q->matrix_mdev = matrix_mdev;
> + }
> +}
> +
> /**
> * assign_adapter_store
> *
(...)
> @@ -682,6 +704,31 @@ vfio_ap_mdev_verify_queues_reserved_for_apqi(struct ap_matrix_mdev *matrix_mdev,
> return 0;
> }
>
> +/**
> + * vfio_ap_mdev_qlinks_for_apqi
See my comment above.
> + *
> + * @matrix_mdev: a matrix mediated device
> + * @apqi: the APQI of one or more APQNs assigned to @matrix_mdev
> + *
> + * Set the link to @matrix_mdev for each queue device bound to the vfio_ap
> + * device driver with an APQN assigned to @matrix_mdev with the specified @apqi.
> + *
> + * Note: If @matrix_mdev is NULL, the link to @matrix_mdev will be severed.
> + */
> +static void vfio_ap_mdev_qlinks_for_apqi(struct ap_matrix_mdev *matrix_mdev,
> + unsigned long apqi)
> +{
> + unsigned long apid;
> + struct vfio_ap_queue *q;
> +
> + for_each_set_bit_inv(apid, matrix_mdev->matrix.apm,
> + matrix_mdev->matrix.apm_max + 1) {
> + q = vfio_ap_get_queue(AP_MKQID(apid, apqi));
> + if (q)
> + q->matrix_mdev = matrix_mdev;
> + }
> +}
> +
> /**
> * assign_domain_store
> *
(...)
> @@ -1270,6 +1319,21 @@ void vfio_ap_mdev_unregister(void)
> mdev_unregister_device(&matrix_dev->device);
> }
>
> +static void vfio_ap_mdev_for_queue(struct vfio_ap_queue *q)
vfio_ap_queue_link_mdev()? It is the other direction from the linking
above.
> +{
> + unsigned long apid = AP_QID_CARD(q->apqn);
> + unsigned long apqi = AP_QID_QUEUE(q->apqn);
> + struct ap_matrix_mdev *matrix_mdev;
> +
> + list_for_each_entry(matrix_mdev, &matrix_dev->mdev_list, node) {
> + if (test_bit_inv(apid, matrix_mdev->matrix.apm) &&
> + test_bit_inv(apqi, matrix_mdev->matrix.aqm)) {
> + q->matrix_mdev = matrix_mdev;
> + break;
> + }
> + }
> +}
> +
> int vfio_ap_mdev_probe_queue(struct ap_queue *queue)
> {
> struct vfio_ap_queue *q;
> @@ -1282,6 +1346,7 @@ int vfio_ap_mdev_probe_queue(struct ap_queue *queue)
> dev_set_drvdata(&queue->ap_dev.device, q);
> q->apqn = queue->qid;
> q->saved_isc = VFIO_AP_ISC_INVALID;
> + vfio_ap_mdev_for_queue(q);
> hash_add(matrix_dev->qtable, &q->qnode, q->apqn);
> mutex_unlock(&matrix_dev->lock);
>
In general, looks sane.
next prev parent reply other threads:[~2020-04-09 15:06 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 19:20 [PATCH v7 00/15] s390/vfio-ap: dynamic configuration support Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 01/15] s390/vfio-ap: store queue struct in hash table for quick access Tony Krowiak
2020-04-08 10:48 ` Cornelia Huck
2020-04-08 15:38 ` Tony Krowiak
2020-04-08 16:27 ` Cornelia Huck
2020-04-08 16:34 ` Tony Krowiak
2020-04-24 3:57 ` Halil Pasic
2020-04-27 13:05 ` Harald Freudenberger
2020-04-27 15:17 ` Halil Pasic
2020-04-27 21:48 ` Tony Krowiak
2020-04-28 10:07 ` Halil Pasic
2020-04-28 10:57 ` Harald Freudenberger
2020-04-28 22:30 ` Tony Krowiak
2020-04-29 7:56 ` Harald Freudenberger
2020-04-29 11:30 ` Halil Pasic
2020-04-28 10:46 ` Harald Freudenberger
2020-04-07 19:20 ` [PATCH v7 02/15] s390/vfio-ap: manage link between queue struct and matrix mdev Tony Krowiak
2020-04-09 15:06 ` Cornelia Huck [this message]
2020-04-10 15:32 ` Tony Krowiak
2020-04-10 15:41 ` Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 03/15] s390/zcrypt: driver callback to indicate resource in use Tony Krowiak
2020-04-14 12:08 ` Cornelia Huck
2020-04-15 17:10 ` Tony Krowiak
2020-04-16 10:05 ` Cornelia Huck
2020-04-16 14:35 ` Tony Krowiak
2020-04-14 12:58 ` Cornelia Huck
2020-04-15 6:08 ` Harald Freudenberger
2020-04-16 9:33 ` Cornelia Huck
2020-04-17 13:54 ` Harald Freudenberger
2020-04-15 17:10 ` Tony Krowiak
2020-04-16 9:37 ` Cornelia Huck
2020-04-24 3:33 ` Halil Pasic
2020-04-24 17:07 ` Tony Krowiak
2020-04-24 18:23 ` Halil Pasic
2020-04-27 21:36 ` Tony Krowiak
2020-04-27 8:20 ` Pierre Morel
2020-04-27 22:24 ` Tony Krowiak
2020-04-28 8:09 ` Pierre Morel
2020-04-28 11:07 ` Harald Freudenberger
2020-04-28 14:37 ` Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 04/15] s390/vfio-ap: implement in-use callback for vfio_ap driver Tony Krowiak
2020-04-16 11:18 ` Cornelia Huck
2020-04-16 14:45 ` Tony Krowiak
2020-04-17 11:23 ` Pierre Morel
2020-04-24 3:13 ` Halil Pasic
2020-04-24 16:58 ` Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 05/15] s390/vfio-ap: introduce shadow CRYCB Tony Krowiak
2020-04-16 11:58 ` Cornelia Huck
2020-04-21 21:39 ` Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 06/15] s390/vfio-ap: sysfs attribute to display the guest CRYCB Tony Krowiak
2020-04-08 10:33 ` Cornelia Huck
2020-04-08 16:38 ` Tony Krowiak
2020-04-08 16:46 ` Cornelia Huck
2020-04-09 14:18 ` Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 07/15] s390/vfio-ap: filter CRYCB bits for unavailable queue devices Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 08/15] s390/vfio_ap: add qlink from ap_matrix_mdev struct to vfio_ap_queue struct Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 09/15] s390/vfio-ap: allow assignment of unavailable AP queues to mdev device Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 10/15] s390/vfio-ap: allow configuration of matrix mdev in use by a KVM guest Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 11/15] s390/vfio-ap: allow hot plug/unplug of AP resources using mdev device Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 12/15] s390/zcrypt: Notify driver on config changed and scan complete callbacks Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 13/15] s390/vfio-ap: handle host AP config change notification Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 14/15] s390/vfio-ap: handle AP bus scan completed notification Tony Krowiak
2020-04-07 19:20 ` [PATCH v7 15/15] s390/vfio-ap: handle probe/remove not due to host AP config changes Tony Krowiak
2020-05-07 15:03 ` [PATCH v7 03/15] s390/zcrypt: driver callback to indicate resource in use 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=20200409170602.4440be0f.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=jjherne@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 \
--cc=pmorel@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