From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kvm@vger.kernel.org, mst@redhat.com, maorg@nvidia.com,
virtualization@lists.linux-foundation.org, jiri@nvidia.com,
leonro@nvidia.com
Subject: Re: [PATCH V1 vfio 0/9] Introduce a vfio driver over virtio devices
Date: Mon, 23 Oct 2023 10:45:48 -0600 [thread overview]
Message-ID: <20231023104548.07b3aa19.alex.williamson@redhat.com> (raw)
In-Reply-To: <20231023162043.GB3952@nvidia.com>
On Mon, 23 Oct 2023 13:20:43 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Mon, Oct 23, 2023 at 10:09:13AM -0600, Alex Williamson wrote:
> > On Mon, 23 Oct 2023 12:42:57 -0300
> > Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > > On Mon, Oct 23, 2023 at 09:33:23AM -0600, Alex Williamson wrote:
> > >
> > > > > Alex,
> > > > > Are you fine to leave the provisioning of the VF including the control
> > > > > of its transitional capability in the device hands as was suggested by
> > > > > Jason ?
> > > >
> > > > If this is the standard we're going to follow, ie. profiling of a
> > > > device is expected to occur prior to the probe of the vfio-pci variant
> > > > driver, then we should get the out-of-tree NVIDIA vGPU driver on board
> > > > with this too.
> > >
> > > Those GPU drivers are using mdev not vfio-pci..
> >
> > The SR-IOV mdev vGPUs rely on the IOMMU backing device support which
> > was removed from upstream.
>
> It wasn't, but it changed forms.
>
> mdev is a sysfs framework for managing lifecycle with GUIDs only.
>
> The thing using mdev can call vfio_register_emulated_iommu_dev() or
> vfio_register_group_dev().
>
> It doesn't matter to the mdev stuff.
>
> The thing using mdev is responsible to get the struct device to pass
> to vfio_register_group_dev()
Are we describing what can be done (possibly limited to out-of-tree
drivers) or what should be done and would be accepted upstream?
I'm under the impression that mdev has been redefined to be more
narrowly focused for emulated IOMMU devices and that devices based
around a PCI VF should be making use of a vfio-pci variant driver.
Are you suggesting it's the vendor's choice based on whether they want
the mdev lifecycle support?
We've defined certain aspects of the vfio-mdev interface as only
available for emulated IOMMU devices, ex. page pinning. Thanks,
Alex
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Yishai Hadas <yishaih@nvidia.com>,
mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org, parav@nvidia.com,
feliu@nvidia.com, jiri@nvidia.com, kevin.tian@intel.com,
joao.m.martins@oracle.com, si-wei.liu@oracle.com,
leonro@nvidia.com, maorg@nvidia.com, jasowang@redhat.com
Subject: Re: [PATCH V1 vfio 0/9] Introduce a vfio driver over virtio devices
Date: Mon, 23 Oct 2023 10:45:48 -0600 [thread overview]
Message-ID: <20231023104548.07b3aa19.alex.williamson@redhat.com> (raw)
In-Reply-To: <20231023162043.GB3952@nvidia.com>
On Mon, 23 Oct 2023 13:20:43 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Mon, Oct 23, 2023 at 10:09:13AM -0600, Alex Williamson wrote:
> > On Mon, 23 Oct 2023 12:42:57 -0300
> > Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > > On Mon, Oct 23, 2023 at 09:33:23AM -0600, Alex Williamson wrote:
> > >
> > > > > Alex,
> > > > > Are you fine to leave the provisioning of the VF including the control
> > > > > of its transitional capability in the device hands as was suggested by
> > > > > Jason ?
> > > >
> > > > If this is the standard we're going to follow, ie. profiling of a
> > > > device is expected to occur prior to the probe of the vfio-pci variant
> > > > driver, then we should get the out-of-tree NVIDIA vGPU driver on board
> > > > with this too.
> > >
> > > Those GPU drivers are using mdev not vfio-pci..
> >
> > The SR-IOV mdev vGPUs rely on the IOMMU backing device support which
> > was removed from upstream.
>
> It wasn't, but it changed forms.
>
> mdev is a sysfs framework for managing lifecycle with GUIDs only.
>
> The thing using mdev can call vfio_register_emulated_iommu_dev() or
> vfio_register_group_dev().
>
> It doesn't matter to the mdev stuff.
>
> The thing using mdev is responsible to get the struct device to pass
> to vfio_register_group_dev()
Are we describing what can be done (possibly limited to out-of-tree
drivers) or what should be done and would be accepted upstream?
I'm under the impression that mdev has been redefined to be more
narrowly focused for emulated IOMMU devices and that devices based
around a PCI VF should be making use of a vfio-pci variant driver.
Are you suggesting it's the vendor's choice based on whether they want
the mdev lifecycle support?
We've defined certain aspects of the vfio-mdev interface as only
available for emulated IOMMU devices, ex. page pinning. Thanks,
Alex
next prev parent reply other threads:[~2023-10-23 16:45 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:42 [PATCH V1 vfio 0/9] Introduce a vfio driver over virtio devices Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 1/9] virtio-pci: Fix common config map for modern device Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 2/9] virtio: Define feature bit for administration virtqueue Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 3/9] virtio-pci: Introduce admin virtqueue Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 4/9] virtio-pci: Introduce admin command sending function Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 5/9] virtio-pci: Introduce admin commands Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 6/9] virtio-pci: Introduce APIs to execute legacy IO " Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 20:33 ` kernel test robot
2023-10-17 20:33 ` kernel test robot
2023-10-22 1:14 ` kernel test robot
2023-10-22 1:14 ` kernel test robot
2023-10-24 21:01 ` Michael S. Tsirkin
2023-10-24 21:01 ` Michael S. Tsirkin
2023-10-25 9:18 ` Yishai Hadas via Virtualization
2023-10-25 10:17 ` Michael S. Tsirkin
2023-10-25 10:17 ` Michael S. Tsirkin
2023-10-25 13:00 ` Yishai Hadas
2023-10-25 13:00 ` Yishai Hadas via Virtualization
2023-10-25 13:04 ` Michael S. Tsirkin
2023-10-25 13:04 ` Michael S. Tsirkin
2023-10-25 13:44 ` Michael S. Tsirkin
2023-10-25 13:44 ` Michael S. Tsirkin
2023-10-25 14:03 ` Yishai Hadas
2023-10-25 14:03 ` Yishai Hadas via Virtualization
2023-10-25 16:31 ` Michael S. Tsirkin
2023-10-25 16:31 ` Michael S. Tsirkin
2023-10-25 9:36 ` Yishai Hadas
2023-10-25 9:36 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 7/9] vfio/pci: Expose vfio_pci_core_setup_barmap() Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 8/9] vfio/pci: Expose vfio_pci_iowrite/read##size() Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 13:42 ` [PATCH V1 vfio 9/9] vfio/virtio: Introduce a vfio driver over virtio devices Yishai Hadas
2023-10-17 13:42 ` Yishai Hadas via Virtualization
2023-10-17 20:24 ` Alex Williamson
2023-10-17 20:24 ` Alex Williamson
2023-10-18 9:01 ` Yishai Hadas
2023-10-18 9:01 ` Yishai Hadas via Virtualization
2023-10-18 12:51 ` Alex Williamson
2023-10-18 12:51 ` Alex Williamson
2023-10-18 13:06 ` Parav Pandit
2023-10-18 13:06 ` Parav Pandit via Virtualization
2023-10-18 16:33 ` Jason Gunthorpe
2023-10-18 18:29 ` Alex Williamson
2023-10-18 18:29 ` Alex Williamson
2023-10-18 19:28 ` Jason Gunthorpe
2023-10-24 19:57 ` Alex Williamson
2023-10-24 19:57 ` Alex Williamson
2023-10-25 14:35 ` Yishai Hadas
2023-10-25 14:35 ` Yishai Hadas via Virtualization
2023-10-25 16:28 ` Michael S. Tsirkin
2023-10-25 16:28 ` Michael S. Tsirkin
2023-10-25 19:13 ` Alex Williamson
2023-10-25 19:13 ` Alex Williamson
2023-10-26 12:08 ` Yishai Hadas
2023-10-26 12:08 ` Yishai Hadas via Virtualization
2023-10-26 12:12 ` Michael S. Tsirkin
2023-10-26 12:12 ` Michael S. Tsirkin
2023-10-26 12:40 ` Parav Pandit
2023-10-26 12:40 ` Parav Pandit via Virtualization
2023-10-26 13:15 ` Michael S. Tsirkin
2023-10-26 13:15 ` Michael S. Tsirkin
2023-10-26 13:28 ` Parav Pandit
2023-10-26 13:28 ` Parav Pandit via Virtualization
2023-10-26 15:06 ` Michael S. Tsirkin
2023-10-26 15:06 ` Michael S. Tsirkin
2023-10-26 15:09 ` Parav Pandit
2023-10-26 15:09 ` Parav Pandit via Virtualization
2023-10-26 15:46 ` Michael S. Tsirkin
2023-10-26 15:46 ` Michael S. Tsirkin
2023-10-26 15:56 ` Parav Pandit
2023-10-26 15:56 ` Parav Pandit via Virtualization
2023-10-26 17:55 ` Alex Williamson
2023-10-26 17:55 ` Alex Williamson
2023-10-26 19:49 ` Michael S. Tsirkin
2023-10-26 19:49 ` Michael S. Tsirkin
2023-10-29 16:13 ` Yishai Hadas via Virtualization
2023-10-29 16:13 ` Yishai Hadas
2023-10-22 8:20 ` [PATCH V1 vfio 0/9] " Yishai Hadas
2023-10-22 8:20 ` Yishai Hadas via Virtualization
2023-10-22 9:12 ` Michael S. Tsirkin
2023-10-22 9:12 ` Michael S. Tsirkin
2023-10-23 15:33 ` Alex Williamson
2023-10-23 15:33 ` Alex Williamson
2023-10-23 15:42 ` Jason Gunthorpe
2023-10-23 16:09 ` Alex Williamson
2023-10-23 16:09 ` Alex Williamson
2023-10-23 16:20 ` Jason Gunthorpe
2023-10-23 16:45 ` Alex Williamson [this message]
2023-10-23 16:45 ` Alex Williamson
2023-10-23 17:27 ` Jason Gunthorpe
2023-10-25 8:34 ` Tian, Kevin
2023-10-25 8:34 ` Tian, Kevin
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=20231023104548.07b3aa19.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=jgg@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.