From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
David Airlie <airlied@linux.ie>,
Eric Farman <farman@linux.ibm.com>,
dri-devel@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>,
linux-s390@vger.kernel.org, "Liu, Yi L" <yi.l.liu@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Jonathan Corbet <corbet@lwn.net>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org,
Tony Krowiak <akrowiak@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [Intel-gfx] [PATCH v2 0/7] Make the rest of the VFIO driver interface use vfio_device
Date: Fri, 29 Apr 2022 14:31:49 -0300 [thread overview]
Message-ID: <20220429173149.GA167483@nvidia.com> (raw)
In-Reply-To: <0-v2-6011bde8e0a1+5f-vfio_mdev_no_group_jgg@nvidia.com>
On Thu, Apr 21, 2022 at 01:28:31PM -0300, Jason Gunthorpe wrote:
> Prior series have transformed other parts of VFIO from working on struct
> device or struct vfio_group into working directly on struct
> vfio_device. Based on that work we now have vfio_device's readily
> available in all the drivers.
>
> Update the rest of the driver facing API to use vfio_device as an input.
>
> The following are switched from struct device to struct vfio_device:
> vfio_register_notifier()
> vfio_unregister_notifier()
> vfio_pin_pages()
> vfio_unpin_pages()
> vfio_dma_rw()
>
> The following group APIs are obsoleted and removed by just using struct
> vfio_device with the above:
> vfio_group_pin_pages()
> vfio_group_unpin_pages()
> vfio_group_iommu_domain()
> vfio_group_get_external_user_from_dev()
>
> To retain the performance of the new device APIs relative to their group
> versions optimize how vfio_group_add_container_user() is used to avoid
> calling it when the driver must already guarantee the device is open and
> the container_users incrd.
>
> The remaining exported VFIO group interfaces are only used by kvm, and are
> addressed by a parallel series.
>
> This series is based on Christoph's gvt rework here:
>
> https://lore.kernel.org/all/5a8b9f48-2c32-8177-1c18-e3bd7bfde558@intel.com/
>
> and so will need the PR merged first.
Hi Alex,
Since all the shared branch PRs are ready, do you have any remarks on
this series and the others before I rebase and repost them?
This one has a few changes to the commit messages outstanding, but v2
didn't have any code changes.
Also, what order would like the different series in - they conflict
with each other a little bit. I suggest this:
- mdev group removal (this one)
- Remove vfio_device_get_from_dev()
https://lore.kernel.org/r/0-v1-7f2292e6b2ba+44839-vfio_get_from_dev_jgg@nvidia.com
- Remove group from kvm
https://lore.kernel.org/r/0-v1-33906a626da1+16b0-vfio_kvm_no_group_jgg@nvidia.com
All of them seem to have got enough reviews now.
I have one more series on this group topic and a few little patches still
It would be great if you could merge the gvt and iommu series together
into your tree toward linux-next so I can post patches against a
stable commit ID so the build-bots can test them.
Thanks,
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
David Airlie <airlied@linux.ie>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Harald Freudenberger <freude@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Jason Herne <jjherne@linux.ibm.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
kvm@vger.kernel.org, Kirti Wankhede <kwankhede@nvidia.com>,
linux-doc@vger.kernel.org, linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sven Schnelle <svens@linux.ibm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.a.wang@intel.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Eric Farman <farman@linux.ibm.com>,
"Liu, Yi L" <yi.l.liu@intel.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 0/7] Make the rest of the VFIO driver interface use vfio_device
Date: Fri, 29 Apr 2022 14:31:49 -0300 [thread overview]
Message-ID: <20220429173149.GA167483@nvidia.com> (raw)
In-Reply-To: <0-v2-6011bde8e0a1+5f-vfio_mdev_no_group_jgg@nvidia.com>
On Thu, Apr 21, 2022 at 01:28:31PM -0300, Jason Gunthorpe wrote:
> Prior series have transformed other parts of VFIO from working on struct
> device or struct vfio_group into working directly on struct
> vfio_device. Based on that work we now have vfio_device's readily
> available in all the drivers.
>
> Update the rest of the driver facing API to use vfio_device as an input.
>
> The following are switched from struct device to struct vfio_device:
> vfio_register_notifier()
> vfio_unregister_notifier()
> vfio_pin_pages()
> vfio_unpin_pages()
> vfio_dma_rw()
>
> The following group APIs are obsoleted and removed by just using struct
> vfio_device with the above:
> vfio_group_pin_pages()
> vfio_group_unpin_pages()
> vfio_group_iommu_domain()
> vfio_group_get_external_user_from_dev()
>
> To retain the performance of the new device APIs relative to their group
> versions optimize how vfio_group_add_container_user() is used to avoid
> calling it when the driver must already guarantee the device is open and
> the container_users incrd.
>
> The remaining exported VFIO group interfaces are only used by kvm, and are
> addressed by a parallel series.
>
> This series is based on Christoph's gvt rework here:
>
> https://lore.kernel.org/all/5a8b9f48-2c32-8177-1c18-e3bd7bfde558@intel.com/
>
> and so will need the PR merged first.
Hi Alex,
Since all the shared branch PRs are ready, do you have any remarks on
this series and the others before I rebase and repost them?
This one has a few changes to the commit messages outstanding, but v2
didn't have any code changes.
Also, what order would like the different series in - they conflict
with each other a little bit. I suggest this:
- mdev group removal (this one)
- Remove vfio_device_get_from_dev()
https://lore.kernel.org/r/0-v1-7f2292e6b2ba+44839-vfio_get_from_dev_jgg@nvidia.com
- Remove group from kvm
https://lore.kernel.org/r/0-v1-33906a626da1+16b0-vfio_kvm_no_group_jgg@nvidia.com
All of them seem to have got enough reviews now.
I have one more series on this group topic and a few little patches still
It would be great if you could merge the gvt and iommu series together
into your tree toward linux-next so I can post patches against a
stable commit ID so the build-bots can test them.
Thanks,
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
David Airlie <airlied@linux.ie>,
Eric Farman <farman@linux.ibm.com>,
dri-devel@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>,
linux-s390@vger.kernel.org, "Liu, Yi L" <yi.l.liu@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Jonathan Corbet <corbet@lwn.net>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH v2 0/7] Make the rest of the VFIO driver interface use vfio_device
Date: Fri, 29 Apr 2022 14:31:49 -0300 [thread overview]
Message-ID: <20220429173149.GA167483@nvidia.com> (raw)
In-Reply-To: <0-v2-6011bde8e0a1+5f-vfio_mdev_no_group_jgg@nvidia.com>
On Thu, Apr 21, 2022 at 01:28:31PM -0300, Jason Gunthorpe wrote:
> Prior series have transformed other parts of VFIO from working on struct
> device or struct vfio_group into working directly on struct
> vfio_device. Based on that work we now have vfio_device's readily
> available in all the drivers.
>
> Update the rest of the driver facing API to use vfio_device as an input.
>
> The following are switched from struct device to struct vfio_device:
> vfio_register_notifier()
> vfio_unregister_notifier()
> vfio_pin_pages()
> vfio_unpin_pages()
> vfio_dma_rw()
>
> The following group APIs are obsoleted and removed by just using struct
> vfio_device with the above:
> vfio_group_pin_pages()
> vfio_group_unpin_pages()
> vfio_group_iommu_domain()
> vfio_group_get_external_user_from_dev()
>
> To retain the performance of the new device APIs relative to their group
> versions optimize how vfio_group_add_container_user() is used to avoid
> calling it when the driver must already guarantee the device is open and
> the container_users incrd.
>
> The remaining exported VFIO group interfaces are only used by kvm, and are
> addressed by a parallel series.
>
> This series is based on Christoph's gvt rework here:
>
> https://lore.kernel.org/all/5a8b9f48-2c32-8177-1c18-e3bd7bfde558@intel.com/
>
> and so will need the PR merged first.
Hi Alex,
Since all the shared branch PRs are ready, do you have any remarks on
this series and the others before I rebase and repost them?
This one has a few changes to the commit messages outstanding, but v2
didn't have any code changes.
Also, what order would like the different series in - they conflict
with each other a little bit. I suggest this:
- mdev group removal (this one)
- Remove vfio_device_get_from_dev()
https://lore.kernel.org/r/0-v1-7f2292e6b2ba+44839-vfio_get_from_dev_jgg@nvidia.com
- Remove group from kvm
https://lore.kernel.org/r/0-v1-33906a626da1+16b0-vfio_kvm_no_group_jgg@nvidia.com
All of them seem to have got enough reviews now.
I have one more series on this group topic and a few little patches still
It would be great if you could merge the gvt and iommu series together
into your tree toward linux-next so I can post patches against a
stable commit ID so the build-bots can test them.
Thanks,
Jason
next prev parent reply other threads:[~2022-04-29 17:32 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:28 [Intel-gfx] [PATCH v2 0/7] Make the rest of the VFIO driver interface use vfio_device Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 1/7] vfio: Make vfio_(un)register_notifier accept a vfio_device Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 1:39 ` [Intel-gfx] " Tian, Kevin
2022-04-22 1:39 ` Tian, Kevin
2022-04-22 17:07 ` [Intel-gfx] " Jason Gunthorpe
2022-04-22 17:07 ` Jason Gunthorpe
2022-04-22 17:07 ` Jason Gunthorpe
2022-04-22 6:21 ` [Intel-gfx] " Christoph Hellwig
2022-04-22 6:21 ` Christoph Hellwig
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 2/7] vfio/ccw: Remove mdev from struct channel_program Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 3/7] vfio/mdev: Pass in a struct vfio_device * to vfio_pin/unpin_pages() Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 1:43 ` [Intel-gfx] " Tian, Kevin
2022-04-22 1:43 ` Tian, Kevin
2022-04-22 1:43 ` Tian, Kevin
2022-04-22 6:22 ` [Intel-gfx] " Christoph Hellwig
2022-04-22 6:22 ` Christoph Hellwig
2022-04-22 20:56 ` [Intel-gfx] " Jason Gunthorpe
2022-04-22 20:56 ` Jason Gunthorpe
2022-04-22 20:56 ` Jason Gunthorpe
2022-04-23 5:15 ` [Intel-gfx] " Christoph Hellwig
2022-04-23 5:15 ` Christoph Hellwig
2022-04-23 12:49 ` [Intel-gfx] " Jason Gunthorpe
2022-04-23 12:49 ` Jason Gunthorpe
2022-04-23 12:49 ` Jason Gunthorpe
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 4/7] vfio/mdev: Pass in a struct vfio_device * to vfio_dma_rw() Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 1:50 ` [Intel-gfx] " Tian, Kevin
2022-04-22 1:50 ` Tian, Kevin
2022-04-22 1:50 ` Tian, Kevin
2022-04-22 17:59 ` [Intel-gfx] " Jason Gunthorpe
2022-04-22 17:59 ` Jason Gunthorpe
2022-04-22 17:59 ` Jason Gunthorpe
2022-04-24 5:52 ` [Intel-gfx] " Tian, Kevin
2022-04-24 5:52 ` Tian, Kevin
2022-04-24 5:52 ` Tian, Kevin
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 5/7] drm/i915/gvt: Change from vfio_group_(un)pin_pages to vfio_(un)pin_pages Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 1:51 ` [Intel-gfx] " Tian, Kevin
2022-04-22 1:51 ` Tian, Kevin
2022-04-22 1:51 ` Tian, Kevin
2022-04-22 6:22 ` [Intel-gfx] " Christoph Hellwig
2022-04-22 6:22 ` Christoph Hellwig
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 6/7] vfio: Remove dead code Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 1:52 ` [Intel-gfx] " Tian, Kevin
2022-04-22 1:52 ` Tian, Kevin
2022-04-22 1:52 ` Tian, Kevin
2022-04-21 16:28 ` [Intel-gfx] [PATCH v2 7/7] vfio: Remove calls to vfio_group_add_container_user() Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-21 16:28 ` Jason Gunthorpe
2022-04-22 2:11 ` [Intel-gfx] " Tian, Kevin
2022-04-22 2:11 ` Tian, Kevin
2022-04-22 2:11 ` Tian, Kevin
2022-04-22 20:55 ` [Intel-gfx] " Jason Gunthorpe
2022-04-22 20:55 ` Jason Gunthorpe
2022-04-22 20:55 ` Jason Gunthorpe
2022-04-29 20:28 ` [Intel-gfx] " Alex Williamson
2022-04-29 20:28 ` Alex Williamson
2022-04-29 20:28 ` Alex Williamson
2022-05-02 16:22 ` [Intel-gfx] " Jason Gunthorpe
2022-05-02 16:22 ` Jason Gunthorpe
2022-05-02 16:22 ` Jason Gunthorpe
2022-04-21 21:25 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Make the rest of the VFIO driver interface use vfio_device (rev3) Patchwork
2022-04-29 17:31 ` Jason Gunthorpe [this message]
2022-04-29 17:31 ` [PATCH v2 0/7] Make the rest of the VFIO driver interface use vfio_device Jason Gunthorpe
2022-04-29 17:31 ` Jason Gunthorpe
2022-04-29 22:22 ` [Intel-gfx] " Alex Williamson
2022-04-29 22:22 ` Alex Williamson
2022-04-29 22:22 ` 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=20220429173149.GA167483@nvidia.com \
--to=jgg@nvidia.com \
--cc=agordeev@linux.ibm.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@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=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=rodrigo.vivi@intel.com \
--cc=svens@linux.ibm.com \
--cc=vneethv@linux.ibm.com \
--cc=yi.l.liu@intel.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.