All of lore.kernel.org
 help / color / mirror / Atom feed
* [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v2 / alternative)
@ 2021-06-14 15:08 ` Christoph Hellwig
  0 siblings, 0 replies; 73+ messages in thread
From: Christoph Hellwig @ 2021-06-14 15:08 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Jason Gunthorpe, Alex Williamson,
	Kirti Wankhede
  Cc: Tony Krowiak, Jason Herne, kvm, Vasily Gorbik, Jonathan Corbet,
	David Airlie, linux-s390, Heiko Carstens, Cornelia Huck,
	linux-doc, dri-devel, Halil Pasic, Christian Borntraeger,
	Rafael J. Wysocki, intel-gfx

This is my alternative take on this series from Jason:

https://lore.kernel.org/dri-devel/87czsszi9i.fsf@redhat.com/T/

The mdev/vfio parts are exactly the same, but this solves the driver core
changes for the direct probing without the in/out flag that Greg hated,
which cause a little more work, but probably make the result better.

Original decription from Jason below:

The mdev bus's core part for managing the lifecycle of devices is mostly
as one would expect for a driver core bus subsystem.

However instead of having a normal 'struct device_driver' and binding the
actual mdev drivers through the standard driver core mechanisms it open
codes this with the struct mdev_parent_ops and provides a single driver
that shims between the VFIO core's struct vfio_device and the actual
device driver.

Instead, allow mdev drivers implement an actual struct mdev_driver and
directly call vfio_register_group_dev() in the probe() function for the
mdev. Arrange to bind the created mdev_device to the mdev_driver that is
provided by the end driver.

The actual execution flow doesn't change much, eg what was
parent_ops->create is now device_driver->probe and it is called at almost
the exact same time - except under the normal control of the driver core.

Ultimately converting all the drivers unlocks a fair number of additional
VFIO simplifications and cleanups.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 73+ messages in thread
* [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v3)
@ 2021-06-15 13:35 Christoph Hellwig
  2021-06-15 13:35 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during sysfs bind Christoph Hellwig
  0 siblings, 1 reply; 73+ messages in thread
From: Christoph Hellwig @ 2021-06-15 13:35 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Jason Gunthorpe, Alex Williamson,
	Kirti Wankhede
  Cc: Tony Krowiak, Jason Herne, kvm, Vasily Gorbik, Jonathan Corbet,
	David Airlie, linux-s390, Heiko Carstens, Cornelia Huck,
	linux-doc, dri-devel, Halil Pasic, Christian Borntraeger,
	Rafael J. Wysocki, intel-gfx

This is my alternative take on this series from Jason:

https://lore.kernel.org/dri-devel/87czsszi9i.fsf@redhat.com/T/

The mdev/vfio parts are exactly the same, but this solves the driver core
changes for the direct probing without the in/out flag that Greg hated,
which cause a little more work, but probably make the result better.

Original decription from Jason below:

The mdev bus's core part for managing the lifecycle of devices is mostly
as one would expect for a driver core bus subsystem.

However instead of having a normal 'struct device_driver' and binding the
actual mdev drivers through the standard driver core mechanisms it open
codes this with the struct mdev_parent_ops and provides a single driver
that shims between the VFIO core's struct vfio_device and the actual
device driver.

Instead, allow mdev drivers implement an actual struct mdev_driver and
directly call vfio_register_group_dev() in the probe() function for the
mdev. Arrange to bind the created mdev_device to the mdev_driver that is
provided by the end driver.

The actual execution flow doesn't change much, eg what was
parent_ops->create is now device_driver->probe and it is called at almost
the exact same time - except under the normal control of the driver core.

Ultimately converting all the drivers unlocks a fair number of additional
VFIO simplifications and cleanups.

Changes since v1:
 - avoid warning spam for successful probes
 - improve the probe_count protection
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 73+ messages in thread
* [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v4)
@ 2021-06-17 14:22 Christoph Hellwig
  2021-06-17 14:22 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during sysfs bind Christoph Hellwig
  0 siblings, 1 reply; 73+ messages in thread
From: Christoph Hellwig @ 2021-06-17 14:22 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Jason Gunthorpe, Alex Williamson,
	Kirti Wankhede
  Cc: Tony Krowiak, Jason Herne, kvm, Vasily Gorbik, Jonathan Corbet,
	David Airlie, linux-s390, Heiko Carstens, Cornelia Huck,
	linux-doc, dri-devel, Halil Pasic, Christian Borntraeger,
	Rafael J. Wysocki, intel-gfx

This is my alternative take on this series from Jason:

https://lore.kernel.org/dri-devel/87czsszi9i.fsf@redhat.com/T/

The mdev/vfio parts are exactly the same, but this solves the driver core
changes for the direct probing without the in/out flag that Greg hated,
which cause a little more work, but probably make the result better.

Original decription from Jason below:

The mdev bus's core part for managing the lifecycle of devices is mostly
as one would expect for a driver core bus subsystem.

However instead of having a normal 'struct device_driver' and binding the
actual mdev drivers through the standard driver core mechanisms it open
codes this with the struct mdev_parent_ops and provides a single driver
that shims between the VFIO core's struct vfio_device and the actual
device driver.

Instead, allow mdev drivers implement an actual struct mdev_driver and
directly call vfio_register_group_dev() in the probe() function for the
mdev. Arrange to bind the created mdev_device to the mdev_driver that is
provided by the end driver.

The actual execution flow doesn't change much, eg what was
parent_ops->create is now device_driver->probe and it is called at almost
the exact same time - except under the normal control of the driver core.

Ultimately converting all the drivers unlocks a fair number of additional
VFIO simplifications and cleanups.

Changes since v3:
 - minor cleanup to avoid the probe_ret variable in really_probe entirely
 - use a saner name for a variable in mdev-mtty
 - use a better driver name in mdev-mtty
 - update the documentation to match the new interface

Changes since v2:
 - avoid warning spam for successful probes
 - improve the probe_count protection
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 73+ messages in thread

end of thread, other threads:[~2021-06-17 14:24 UTC | newest]

Thread overview: 73+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-06-14 15:08 [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v2 / alternative) Christoph Hellwig
2021-06-14 15:08 ` Christoph Hellwig
2021-06-14 15:08 ` [Intel-gfx] [PATCH 01/10] driver core: Pull required checks into driver_probe_device() Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15  5:16   ` [Intel-gfx] " Greg Kroah-Hartman
2021-06-15  5:16     ` Greg Kroah-Hartman
2021-06-15  5:16     ` Greg Kroah-Hartman
2021-06-15 10:27   ` [Intel-gfx] " Cornelia Huck
2021-06-15 10:27     ` Cornelia Huck
2021-06-15 10:27     ` Cornelia Huck
2021-06-14 15:08 ` [Intel-gfx] [PATCH 02/10] driver core: Better distinguish probe errors in really_probe Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-14 18:47   ` [Intel-gfx] " Kirti Wankhede
2021-06-14 18:47     ` Kirti Wankhede
2021-06-14 18:47     ` Kirti Wankhede
2021-06-15  5:17   ` [Intel-gfx] " Greg Kroah-Hartman
2021-06-15  5:17     ` Greg Kroah-Hartman
2021-06-15  5:17     ` Greg Kroah-Hartman
2021-06-15  5:48     ` [Intel-gfx] " Christoph Hellwig
2021-06-15  5:48       ` Christoph Hellwig
2021-06-14 15:08 ` [Intel-gfx] [PATCH 03/10] driver core: Flow the return code from ->probe() through to sysfs bind Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15  5:18   ` [Intel-gfx] " Greg Kroah-Hartman
2021-06-15  5:18     ` Greg Kroah-Hartman
2021-06-15  5:18     ` Greg Kroah-Hartman
2021-06-15 10:31   ` [Intel-gfx] " Cornelia Huck
2021-06-15 10:31     ` Cornelia Huck
2021-06-15 10:31     ` Cornelia Huck
2021-06-14 15:08 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during " Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-14 22:43   ` [Intel-gfx] " Jason Gunthorpe
2021-06-14 22:43     ` Jason Gunthorpe
2021-06-14 22:43     ` Jason Gunthorpe
2021-06-14 15:08 ` [Intel-gfx] [PATCH 05/10] driver core: Export device_driver_attach() Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15  5:20   ` [Intel-gfx] " Greg Kroah-Hartman
2021-06-15  5:20     ` Greg Kroah-Hartman
2021-06-15  5:20     ` Greg Kroah-Hartman
2021-06-15 10:49   ` [Intel-gfx] " Cornelia Huck
2021-06-15 10:49     ` Cornelia Huck
2021-06-15 10:49     ` Cornelia Huck
2021-06-14 15:08 ` [Intel-gfx] [PATCH 06/10] vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICE Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15 10:50   ` [Intel-gfx] " Cornelia Huck
2021-06-15 10:50     ` Cornelia Huck
2021-06-15 10:50     ` Cornelia Huck
2021-06-14 15:08 ` [Intel-gfx] [PATCH 07/10] vfio/mdev: Allow the mdev_parent_ops to specify the device driver to bind Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15 10:54   ` [Intel-gfx] " Cornelia Huck
2021-06-15 10:54     ` Cornelia Huck
2021-06-15 10:54     ` Cornelia Huck
2021-06-14 15:08 ` [Intel-gfx] [PATCH 08/10] vfio/mtty: Convert to use vfio_register_group_dev() Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-14 15:08 ` [Intel-gfx] [PATCH 09/10] vfio/mdpy: " Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-14 15:08 ` [Intel-gfx] [PATCH 10/10] vfio/mbochs: " Christoph Hellwig
2021-06-14 15:08   ` Christoph Hellwig
2021-06-15  0:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] driver core: Pull required checks into driver_probe_device() Patchwork
2021-06-15  0:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-06-15  0:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-15  5:21 ` [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v2 / alternative) Greg Kroah-Hartman
2021-06-15  5:21   ` Greg Kroah-Hartman
2021-06-15  5:21   ` Greg Kroah-Hartman
2021-06-15  5:50   ` [Intel-gfx] " Christoph Hellwig
2021-06-15  5:50     ` Christoph Hellwig
2021-06-15 15:27     ` [Intel-gfx] " Jason Gunthorpe
2021-06-15 15:27       ` Jason Gunthorpe
2021-06-15 15:27       ` Jason Gunthorpe
2021-06-15  9:37 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [01/10] driver core: Pull required checks into driver_probe_device() Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2021-06-15 13:35 [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v3) Christoph Hellwig
2021-06-15 13:35 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during sysfs bind Christoph Hellwig
2021-06-15 14:03   ` Cornelia Huck
2021-06-15 19:36   ` Alex Williamson
2021-06-17 14:22 [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v4) Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during sysfs bind Christoph Hellwig

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.