From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, Kirti Wankhede <kwankhede@nvidia.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
Leon Romanovsky <leonro@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>
Subject: Re: [PATCH v2 02/13] vfio/mdev: Allow the mdev_parent_ops to specify the device driver to bind
Date: Wed, 28 Apr 2021 14:41:53 +0200 [thread overview]
Message-ID: <20210428124153.GA28566@lst.de> (raw)
In-Reply-To: <CAPcyv4g=MFtZMVZPn8AtTX6NyweF25nuFNVBu7pg_QSP+EGE+g@mail.gmail.com>
On Wed, Apr 28, 2021 at 12:56:21AM -0700, Dan Williams wrote:
> > I still think this going the wrong way. Why can't we enhance the core
> > driver code with a version of device_bind_driver() that does call into
> > ->probe? That probably seems like a better model for those existing
> > direct users of device_bind_driver or device_attach with a pre-set
> > ->drv anyway.
>
> Wouldn't that just be "export device_driver_attach()" so that drivers
> can implement their own custom bind implementation?
That looks like it might be all that is needed.
next prev parent reply other threads:[~2021-04-28 12:41 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 20:00 [Intel-gfx] [PATCH v2 00/13] Remove vfio_mdev.c, mdev_parent_ops and more Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` [Intel-gfx] [PATCH v2 01/13] vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICE Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-27 11:05 ` [Intel-gfx] " Cornelia Huck
2021-04-27 11:05 ` Cornelia Huck
2021-04-27 11:05 ` Cornelia Huck
2021-04-26 20:00 ` [PATCH v2 02/13] vfio/mdev: Allow the mdev_parent_ops to specify the device driver to bind Jason Gunthorpe
2021-04-27 12:32 ` Cornelia Huck
2021-04-27 23:20 ` Jason Gunthorpe
2021-04-28 6:03 ` Christoph Hellwig
2021-04-28 7:56 ` Dan Williams
2021-04-28 12:41 ` Christoph Hellwig [this message]
2021-04-28 14:00 ` Jason Gunthorpe
2021-04-28 19:58 ` Dan Williams
2021-04-28 23:38 ` Jason Gunthorpe
2021-04-29 0:00 ` Dave Jiang
2021-05-26 0:42 ` Jason Gunthorpe
2021-05-26 1:42 ` Dan Williams
2021-05-27 11:44 ` Christoph Hellwig
2021-05-27 14:53 ` Jason Gunthorpe
2021-05-27 15:13 ` Christoph Hellwig
2021-04-29 6:51 ` Christoph Hellwig
2021-05-04 9:36 ` Christoph Hellwig
2021-05-04 11:30 ` Jason Gunthorpe
2021-04-28 6:44 ` Leon Romanovsky
2021-04-28 14:14 ` Jason Gunthorpe
2021-04-28 14:24 ` Leon Romanovsky
2021-04-26 20:00 ` [PATCH v2 03/13] vfio/mtty: Convert to use vfio_register_group_dev() Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 04/13] vfio/mdpy: " Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 05/13] vfio/mbochs: " Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 06/13] vfio/ap_ops: " Jason Gunthorpe
2021-05-04 14:42 ` Tony Krowiak
2021-05-04 16:55 ` Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 07/13] vfio/ccw: " Jason Gunthorpe
2021-04-27 20:06 ` Eric Farman
2021-04-27 22:10 ` Jason Gunthorpe
2021-04-28 12:55 ` Eric Farman
2021-04-28 13:21 ` Jason Gunthorpe
2021-04-28 17:09 ` Cornelia Huck
2021-04-28 17:20 ` Jason Gunthorpe
2021-04-29 11:58 ` Cornelia Huck
2021-04-29 18:13 ` Jason Gunthorpe
2021-04-30 12:31 ` Cornelia Huck
2021-04-30 17:19 ` Jason Gunthorpe
2021-05-03 10:54 ` s390 common I/O layer locking (was: [PATCH v2 07/13] vfio/ccw: Convert to use vfio_register_group_dev()) Cornelia Huck
2021-05-04 15:10 ` s390 common I/O layer locking Vineeth Vijayan
2021-07-24 13:24 ` Christoph Hellwig
2021-08-03 14:27 ` Vineeth Vijayan
2021-08-10 15:00 ` Cornelia Huck
2021-04-26 20:00 ` [Intel-gfx] [PATCH v2 08/13] vfio/gvt: Convert to use vfio_register_group_dev() Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 09/13] vfio/mdev: Remove vfio_mdev.c Jason Gunthorpe
2021-04-28 6:07 ` Christoph Hellwig
2021-04-28 6:36 ` Greg Kroah-Hartman
2021-04-28 12:53 ` Jason Gunthorpe
2021-04-29 6:53 ` Christoph Hellwig
2021-04-29 6:56 ` Greg Kroah-Hartman
2021-05-03 17:32 ` Jason Gunthorpe
2021-05-04 9:38 ` Christoph Hellwig
2021-05-04 16:20 ` Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 10/13] vfio/mdev: Remove mdev_parent_ops dev_attr_groups Jason Gunthorpe
2021-04-26 20:00 ` [Intel-gfx] [PATCH v2 11/13] vfio/mdev: Remove mdev_parent_ops Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 12/13] vfio/mdev: Use the driver core to create the 'remove' file Jason Gunthorpe
2021-04-26 20:00 ` [PATCH v2 13/13] vfio/mdev: Remove mdev drvdata Jason Gunthorpe
2021-04-27 21:30 ` [Intel-gfx] [PATCH v2 00/13] Remove vfio_mdev.c, mdev_parent_ops and more Alex Williamson
2021-04-27 21:30 ` Alex Williamson
2021-04-27 21:30 ` Alex Williamson
2021-04-27 22:20 ` [Intel-gfx] " Jason Gunthorpe
2021-04-27 22:20 ` Jason Gunthorpe
2021-04-27 22:20 ` Jason Gunthorpe
2021-04-27 22:49 ` [Intel-gfx] " Alex Williamson
2021-04-27 22:49 ` Alex Williamson
2021-04-27 22:49 ` Alex Williamson
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=20210428124153.GA28566@lst.de \
--to=hch@lst.de \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=cohuck@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=leonro@nvidia.com \
--cc=mgurtovoy@nvidia.com \
--cc=targupta@nvidia.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.