From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>,
linux-s390@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
intel-gfx@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v4)
Date: Tue, 22 Jun 2021 21:05:50 -0300 [thread overview]
Message-ID: <20210623000550.GI2371267@nvidia.com> (raw)
In-Reply-To: <20210617142218.1877096-1-hch@lst.de>
On Thu, Jun 17, 2021 at 04:22:08PM +0200, Christoph Hellwig wrote:
> 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.
I did some testing and it looks good, thanks
I see Alex has this in hch-mdev-direct-v4 in linux-next now, so
expecting this to be in the next merge window?
The AP prep patches seemed sorted so I'll resend the AP patch in three
weeks
Jason
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-06-23 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 01/10] driver core: Pull required checks into driver_probe_device() Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 02/10] driver core: Better distinguish probe errors in really_probe Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 03/10] driver core: Flow the return code from ->probe() through to sysfs bind Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 04/10] driver core: Don't return EPROBE_DEFER to userspace during " Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 05/10] driver core: Export device_driver_attach() Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 06/10] vfio/mdev: Remove CONFIG_VFIO_MDEV_DEVICE Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 07/10] vfio/mdev: Allow the mdev_parent_ops to specify the device driver to bind Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 08/10] vfio/mtty: Convert to use vfio_register_group_dev() Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 09/10] vfio/mdpy: " Christoph Hellwig
2021-06-17 14:22 ` [Intel-gfx] [PATCH 10/10] vfio/mbochs: " Christoph Hellwig
2021-06-17 14:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] driver core: Pull required checks into driver_probe_device() Patchwork
2021-06-17 15:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-17 17:12 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-23 0:05 ` Jason Gunthorpe [this message]
2021-06-23 1:21 ` [Intel-gfx] Allow mdev drivers to directly create the vfio_device (v4) 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=20210623000550.GI2371267@nvidia.com \
--to=jgg@nvidia.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=rafael@kernel.org \
/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