From: Tony Krowiak <akrowiak@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: borntraeger@de.ibm.com, cohuck@redhat.com, frankja@linux.ibm.com,
david@redhat.com, mjrosato@linux.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, pmorel@linux.ibm.com,
pasic@linux.ibm.com, alex.williamson@redhat.com,
kwankhede@nvidia.com
Subject: Re: [PATCH v4 1/7] s390: vfio-ap: Refactor vfio_ap driver probe and remove callbacks
Date: Mon, 17 Jun 2019 10:24:21 -0400 [thread overview]
Message-ID: <8817a913-b574-3bf4-6ef8-b8f1c5a4728e@linux.ibm.com> (raw)
In-Reply-To: <534f8ef2-ac7a-bda3-54cf-d475b2a47c02@linux.ibm.com>
On 6/17/19 4:27 AM, Harald Freudenberger wrote:
> On 13.06.19 21:39, Tony Krowiak wrote:
>> In order to limit the number of private mdev functions called from the
>> vfio_ap device driver as well as to provide a landing spot for dynamic
>> configuration code related to binding/unbinding AP queue devices to/from
>> the vfio_ap driver, the following changes are being introduced:
>>
>> * Move code from the vfio_ap driver's probe callback into a function
>> defined in the mdev private operations file.
>>
>> * Move code from the vfio_ap driver's remove callback into a function
>> defined in the mdev private operations file.
>>
>> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
>> ---
>> drivers/s390/crypto/vfio_ap_drv.c | 27 ++++++++++-----------------
>> drivers/s390/crypto/vfio_ap_ops.c | 28 ++++++++++++++++++++++++++++
>> drivers/s390/crypto/vfio_ap_private.h | 6 +++---
>> 3 files changed, 41 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/s390/crypto/vfio_ap_drv.c b/drivers/s390/crypto/vfio_ap_drv.c
>> index 003662aa8060..3c60df70891b 100644
>> --- a/drivers/s390/crypto/vfio_ap_drv.c
>> +++ b/drivers/s390/crypto/vfio_ap_drv.c
>> @@ -49,15 +49,15 @@ MODULE_DEVICE_TABLE(vfio_ap, ap_queue_ids);
>> */
>> static int vfio_ap_queue_dev_probe(struct ap_device *apdev)
>> {
>> - struct vfio_ap_queue *q;
>> -
>> - q = kzalloc(sizeof(*q), GFP_KERNEL);
>> - if (!q)
>> - return -ENOMEM;
>> - dev_set_drvdata(&apdev->device, q);
>> - q->apqn = to_ap_queue(&apdev->device)->qid;
>> - q->saved_isc = VFIO_AP_ISC_INVALID;
>> + int ret;
>> + struct ap_queue *queue = to_ap_queue(&apdev->device);
>> +
>> + ret = vfio_ap_mdev_probe_queue(queue);
>> + if (ret)
>> + return ret;
>> +
>> return 0;
> A simple
> return vfio_ap_mdev_probe_queue(queue);
> would be enough.
True.
>> +
>> }
>>
>> /**
>> @@ -68,17 +68,10 @@ static int vfio_ap_queue_dev_probe(struct ap_device *apdev)
>> */
>> static void vfio_ap_queue_dev_remove(struct ap_device *apdev)
>> {
>> - struct vfio_ap_queue *q;
>> - int apid, apqi;
>> + struct ap_queue *queue = to_ap_queue(&apdev->device);
>>
>> mutex_lock(&matrix_dev->lock);
>> - q = dev_get_drvdata(&apdev->device);
>> - dev_set_drvdata(&apdev->device, NULL);
>> - apid = AP_QID_CARD(q->apqn);
>> - apqi = AP_QID_QUEUE(q->apqn);
>> - vfio_ap_mdev_reset_queue(apid, apqi, 1);
>> - vfio_ap_irq_disable(q);
>> - kfree(q);
>> + vfio_ap_mdev_remove_queue(queue);
>> mutex_unlock(&matrix_dev->lock);
>> }
>>
>> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
>> index 015174ff6f0a..bf2ab02b9a0b 100644
>> --- a/drivers/s390/crypto/vfio_ap_ops.c
>> +++ b/drivers/s390/crypto/vfio_ap_ops.c
>> @@ -1302,3 +1302,31 @@ void vfio_ap_mdev_unregister(void)
>> {
>> mdev_unregister_device(&matrix_dev->device);
>> }
>> +
>> +int vfio_ap_mdev_probe_queue(struct ap_queue *queue)
>> +{
>> + struct vfio_ap_queue *q;
>> +
>> + q = kzalloc(sizeof(*q), GFP_KERNEL);
>> + if (!q)
>> + return -ENOMEM;
>> + dev_set_drvdata(&queue->ap_dev.device, q);
>> + q->apqn = queue->qid;
>> + q->saved_isc = VFIO_AP_ISC_INVALID;
>> +
>> + return 0;
>> +}
>> +
>> +void vfio_ap_mdev_remove_queue(struct ap_queue *queue)
>> +{
>> + struct vfio_ap_queue *q;
>> + int apid, apqi;
>> +
>> + q = dev_get_drvdata(&queue->ap_dev.device);
>> + dev_set_drvdata(&queue->ap_dev.device, NULL);
>> + apid = AP_QID_CARD(q->apqn);
>> + apqi = AP_QID_QUEUE(q->apqn);
>> + vfio_ap_mdev_reset_queue(apid, apqi, 1);
>> + vfio_ap_irq_disable(q);
>> + kfree(q);
>> +}
>> diff --git a/drivers/s390/crypto/vfio_ap_private.h b/drivers/s390/crypto/vfio_ap_private.h
>> index f46dde56b464..5cc3c2ebf151 100644
>> --- a/drivers/s390/crypto/vfio_ap_private.h
>> +++ b/drivers/s390/crypto/vfio_ap_private.h
>> @@ -90,8 +90,6 @@ struct ap_matrix_mdev {
>>
>> extern int vfio_ap_mdev_register(void);
>> extern void vfio_ap_mdev_unregister(void);
>> -int vfio_ap_mdev_reset_queue(unsigned int apid, unsigned int apqi,
>> - unsigned int retry);
>>
>> struct vfio_ap_queue {
>> struct ap_matrix_mdev *matrix_mdev;
>> @@ -100,5 +98,7 @@ struct vfio_ap_queue {
>> #define VFIO_AP_ISC_INVALID 0xff
>> unsigned char saved_isc;
>> };
>> -struct ap_queue_status vfio_ap_irq_disable(struct vfio_ap_queue *q);
>> +int vfio_ap_mdev_probe_queue(struct ap_queue *queue);
>> +void vfio_ap_mdev_remove_queue(struct ap_queue *queue);
>> +
>> #endif /* _VFIO_AP_PRIVATE_H_ */
>
next prev parent reply other threads:[~2019-06-17 14:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 19:39 [PATCH v4 0/7] s390: vfio-ap: dynamic configuration support Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 1/7] s390: vfio-ap: Refactor vfio_ap driver probe and remove callbacks Tony Krowiak
2019-06-17 8:27 ` Harald Freudenberger
2019-06-17 14:24 ` Tony Krowiak [this message]
2019-06-18 16:14 ` Cornelia Huck
2019-06-19 12:31 ` Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 2/7] s390: vfio-ap: wait for queue empty on queue reset Tony Krowiak
2019-06-17 8:47 ` Harald Freudenberger
2019-06-17 14:29 ` Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 3/7] s390: zcrypt: driver callback to indicate resource in use Tony Krowiak
2019-06-17 9:28 ` Harald Freudenberger
2019-06-17 14:37 ` Tony Krowiak
2019-06-18 16:25 ` Cornelia Huck
2019-06-19 13:04 ` Tony Krowiak
2019-06-26 21:13 ` Tony Krowiak
2019-06-27 7:25 ` Cornelia Huck
2019-06-27 12:59 ` Tony Krowiak
2019-07-01 19:26 ` Cornelia Huck
2019-07-08 14:27 ` Tony Krowiak
2019-07-09 10:49 ` Cornelia Huck
2019-07-09 21:11 ` Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 4/7] s390: vfio-ap: implement in-use callback for vfio_ap driver Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 5/7] s390: vfio-ap: allow assignment of unavailable AP resources to mdev device Tony Krowiak
2019-06-17 10:05 ` Harald Freudenberger
2019-06-17 15:07 ` Tony Krowiak
2019-06-18 6:49 ` Harald Freudenberger
2019-06-19 13:39 ` Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 6/7] s390: vfio-ap: allow hot plug/unplug of AP resources using " Tony Krowiak
2019-06-13 19:39 ` [PATCH v4 7/7] s390: vfio-ap: update documentation Tony Krowiak
2019-06-17 11:42 ` Harald Freudenberger
2019-06-17 15:21 ` Tony Krowiak
2019-07-09 15:30 ` [PATCH v4 0/7] s390: vfio-ap: dynamic configuration support Halil Pasic
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=8817a913-b574-3bf4-6ef8-b8f1c5a4728e@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=heiko.carstens@de.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 \
--cc=schwidefsky@de.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;
as well as URLs for NNTP newsgroup(s).