All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>, Pierre Morel <pmorel@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	frankja@linux.ibm.com, akrowiak@linux.ibm.com,
	pasic@linux.ibm.com, david@redhat.com, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, freude@linux.ibm.com
Subject: Re: [PATCH v2 1/1] s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem
Date: Tue, 19 Feb 2019 10:44:25 +0100	[thread overview]
Message-ID: <c23816b4-e24d-7cf7-8018-a3c085eef9f3@de.ibm.com> (raw)
In-Reply-To: <20190219102204.5e050b76.cohuck@redhat.com>



On 19.02.2019 10:22, Cornelia Huck wrote:
> On Mon, 18 Feb 2019 19:08:48 +0100
> Pierre Morel <pmorel@linux.ibm.com> wrote:
> 
>> Libudev relies on having a subsystem link for non-root devices. To
>> avoid libudev (and potentially other userspace tools) choking on the
>> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
>> bus subsytem, and make the matrix device reside within it.
>>
>> Doing this we need to suppress the forced link from the matrix device to
>> the vfio_ap driver and we suppress the device_type we do not need
> 
> s/suppress/remove/ ?
> 
>> anymore.
>>
>> Since the associated matrix driver is not the vfio_ap driver any more,
>> we have to change the search for the devices on the vfio_ap driver in
>> the function vfio_ap_verify_queue_reserved.
>>
>> Reported-by: Marc Hartmayer <mhartmay@linux.ibm.com>
>> Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>>  drivers/s390/crypto/vfio_ap_drv.c     | 48 +++++++++++++++++++++++++++++------
>>  drivers/s390/crypto/vfio_ap_ops.c     |  4 +--
>>  drivers/s390/crypto/vfio_ap_private.h |  1 +
>>  3 files changed, 43 insertions(+), 10 deletions(-)
> 
> (...)
> 
>> @@ -62,6 +58,27 @@ static void vfio_ap_matrix_dev_release(struct device *dev)
>>  	kfree(matrix_dev);
>>  }
>>  
>> +static int matrix_bus_match(struct device *dev, struct device_driver *drv)
>> +{
>> +	return 1;
>> +}
>> +
>> +static struct bus_type matrix_bus = {
>> +	.name = "vfio_ap",
>> +	.match = &matrix_bus_match,
>> +};
>> +
>> +static int matrix_probe(struct device *dev)
>> +{
>> +	return 0;
>> +}
> 
> I don't think you need this (the important function is the match
> function of the bus).

Yes, with 

diff --git a/drivers/s390/crypto/vfio_ap_drv.c b/drivers/s390/crypto/vfio_ap_drv.c
index 8e45559795429..8ceec41afe322 100644
--- a/drivers/s390/crypto/vfio_ap_drv.c
+++ b/drivers/s390/crypto/vfio_ap_drv.c
@@ -68,15 +68,9 @@ static struct bus_type matrix_bus = {
        .match = &matrix_bus_match,
 };
 
-static int matrix_probe(struct device *dev)
-{
-       return 0;
-}
-
 static struct device_driver matrix_driver = {
        .name = "vfio_ap",
        .bus = &matrix_bus,
-       .probe = matrix_probe,
 };
 
 static int vfio_ap_matrix_dev_create(void)

on top things still look fine.


> 
>> +
>> +static struct device_driver matrix_driver = {
>> +	.name = "vfio_ap",
>> +	.bus = &matrix_bus,
>> +	.probe = matrix_probe,
>> +};
>> +
>>  static int vfio_ap_matrix_dev_create(void)
>>  {
>>  	int ret;
> 
> It's a bit annoying that we need to introduce a bus that basically does
> nothing, but I think this looks sane.
> 
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> 


  reply	other threads:[~2019-02-19  9:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 18:08 [PATCH v2 0/1] s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem Pierre Morel
2019-02-18 18:08 ` [PATCH v2 1/1] " Pierre Morel
2019-02-19  8:13   ` Christian Borntraeger
2019-02-19  9:22   ` Cornelia Huck
2019-02-19  9:44     ` Christian Borntraeger [this message]
2019-02-21 11:34       ` Pierre Morel
2019-02-19 17:45   ` Halil Pasic
2019-02-19 18:52   ` Tony Krowiak
2019-02-19 21:31     ` Pierre Morel
2019-02-20  9:27       ` Cornelia Huck
2019-02-20 12:51         ` Halil Pasic
2019-02-21 12:10           ` Pierre Morel
2019-02-21 12:35             ` Christian Borntraeger
2019-02-21 12:51               ` Pierre Morel
2019-02-21 13:01                 ` Christian Borntraeger
2019-02-21 13:20                   ` Pierre Morel
2019-02-20 13:12   ` Harald Freudenberger
2019-02-21  7:37     ` Christian Borntraeger
2019-02-21  8:07       ` Harald Freudenberger
2019-02-21  9:57       ` Pierre Morel

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=c23816b4-e24d-7cf7-8018-a3c085eef9f3@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=akrowiak@linux.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=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.