Displaying 20 results from an estimated 924 matches for "vfio".
2016 Aug 30
6
[PATCH v2 0/2] vfio: blacklist legacy virtio devices
Legacy virtio devices always bypassed an IOMMU, so using them with vfio was
never safe. This adds a quirk detecting these and disabling VFIO unless the
noiommu mode is used. At the moment, this only applies to virtio-pci devices.
The patch might make sense on stable as well.
Michael S. Tsirkin (2):
vfio: report group noiommu status
vfio: add virtio pci quirk...
2016 Aug 30
6
[PATCH v2 0/2] vfio: blacklist legacy virtio devices
Legacy virtio devices always bypassed an IOMMU, so using them with vfio was
never safe. This adds a quirk detecting these and disabling VFIO unless the
noiommu mode is used. At the moment, this only applies to virtio-pci devices.
The patch might make sense on stable as well.
Michael S. Tsirkin (2):
vfio: report group noiommu status
vfio: add virtio pci quirk...
2016 Apr 18
5
[PATCH RFC 0/3] virtio-pci: iommu support
This is an attempt to allow enabling IOMMU for DMA.
Design:
- new feature bit IOMMU_PLATFORM which means
host won't bypass IOMMU
- virtio core uses DMA API if it sees IOMMU_PLATFORM
- add quirk for vfio to disable device unless IOMMU_PLATFORM is set
or the no-iommu mode is enabled
- while I'm not sure how it will be used, it seems like a good idea to
also have ability to distinguish between a legacy device and one
where iommu is bypassed intentionally. To this end, add anothe...
2016 Apr 18
5
[PATCH RFC 0/3] virtio-pci: iommu support
This is an attempt to allow enabling IOMMU for DMA.
Design:
- new feature bit IOMMU_PLATFORM which means
host won't bypass IOMMU
- virtio core uses DMA API if it sees IOMMU_PLATFORM
- add quirk for vfio to disable device unless IOMMU_PLATFORM is set
or the no-iommu mode is enabled
- while I'm not sure how it will be used, it seems like a good idea to
also have ability to distinguish between a legacy device and one
where iommu is bypassed intentionally. To this end, add anothe...
2019 Oct 17
3
[PATCH V4 3/6] mdev: introduce device specific ops
On Thu, 17 Oct 2019 18:48:33 +0800
Jason Wang <jasowang at redhat.com> wrote:
> Currently, except for the create and remove, the rest of
> mdev_parent_ops is designed for vfio-mdev driver only and may not help
> for kernel mdev driver. With the help of class id, this patch
> introduces device specific callbacks inside mdev_device
> structure. This allows different set of callback to be used by
> vfio-mdev and virtio-mdev.
>
> Signed-off-by: Jason Wang...
2019 Oct 17
3
[PATCH V4 3/6] mdev: introduce device specific ops
On Thu, 17 Oct 2019 18:48:33 +0800
Jason Wang <jasowang at redhat.com> wrote:
> Currently, except for the create and remove, the rest of
> mdev_parent_ops is designed for vfio-mdev driver only and may not help
> for kernel mdev driver. With the help of class id, this patch
> introduces device specific callbacks inside mdev_device
> structure. This allows different set of callback to be used by
> vfio-mdev and virtio-mdev.
>
> Signed-off-by: Jason Wang...
2016 Aug 30
4
[PATCH v2 2/2] vfio: add virtio pci quirk
...Aug 2016 05:27:17 +0300
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM
> to signal they are safe to use with an IOMMU.
>
> Without this bit, exposing the device to userspace is unsafe, so probe
> and fail VFIO initialization unless noiommu is enabled.
>
> Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> ---
> drivers/vfio/pci/vfio_pci_private.h | 1 +
> drivers/vfio/pci/vfio_pci.c | 14 ++++
> drivers/vfio/pci/vfio_pci_virtio.c | 140 ++++++++++++++++++++++++++...
2016 Aug 30
4
[PATCH v2 2/2] vfio: add virtio pci quirk
...Aug 2016 05:27:17 +0300
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM
> to signal they are safe to use with an IOMMU.
>
> Without this bit, exposing the device to userspace is unsafe, so probe
> and fail VFIO initialization unless noiommu is enabled.
>
> Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> ---
> drivers/vfio/pci/vfio_pci_private.h | 1 +
> drivers/vfio/pci/vfio_pci.c | 14 ++++
> drivers/vfio/pci/vfio_pci_virtio.c | 140 ++++++++++++++++++++++++++...
2016 Apr 18
0
[PATCH RFC 2/3] vfio: report group noiommu status
When using vfio, callers might want to know whether device is added to a
regular group or an non-iommu group.
Report this status from vfio_add_group_dev.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
drivers/vfio/pci/vfio_pci.c | 2 +-
drivers/vfio/platform/vfio_platform_commo...
2019 Sep 24
1
[PATCH V2 2/8] mdev: class id support
On Tue, 24 Sep 2019 21:53:26 +0800
Jason Wang <jasowang at redhat.com> wrote:
> Mdev bus only supports vfio driver right now, so it doesn't implement
> match method. But in the future, we may add drivers other than vfio,
> the first driver could be virtio-mdev. This means we need to add
> device class id support in bus match method to pair the mdev device
> and mdev driver correctly.
>...
2016 Aug 30
2
[PATCH v2 2/2] vfio: add virtio pci quirk
...t at redhat.com> wrote:
> >
> > > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM
> > > to signal they are safe to use with an IOMMU.
> > >
> > > Without this bit, exposing the device to userspace is unsafe, so probe
> > > and fail VFIO initialization unless noiommu is enabled.
> > >
> > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> > > ---
> > > drivers/vfio/pci/vfio_pci_private.h | 1 +
> > > drivers/vfio/pci/vfio_pci.c | 14 ++++
> > > drivers/...
2016 Aug 30
2
[PATCH v2 2/2] vfio: add virtio pci quirk
...t at redhat.com> wrote:
> >
> > > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM
> > > to signal they are safe to use with an IOMMU.
> > >
> > > Without this bit, exposing the device to userspace is unsafe, so probe
> > > and fail VFIO initialization unless noiommu is enabled.
> > >
> > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> > > ---
> > > drivers/vfio/pci/vfio_pci_private.h | 1 +
> > > drivers/vfio/pci/vfio_pci.c | 14 ++++
> > > drivers/...
2019 Sep 17
1
[RFC PATCH 1/2] mdev: device id support
> From: Jason Wang
> Sent: Thursday, September 12, 2019 5:40 PM
>
> Mdev bus only support vfio driver right now, so it doesn't implement
> match method. But in the future, we may add drivers other than vfio,
> one example is virtio-mdev[1] driver. This means we need to add device
> id support in bus match method to pair the mdev device and mdev driver
> correctly.
"devi...
2019 Oct 23
2
[PATCH V5 1/6] mdev: class id support
On Wed, 23 Oct 2019 21:07:47 +0800
Jason Wang <jasowang at redhat.com> wrote:
> Mdev bus only supports vfio driver right now, so it doesn't implement
> match method. But in the future, we may add drivers other than vfio,
> the first driver could be virtio-mdev. This means we need to add
> device class id support in bus match method to pair the mdev device
> and mdev driver correctly.
>...
2019 Oct 23
2
[PATCH V5 1/6] mdev: class id support
On Wed, 23 Oct 2019 21:07:47 +0800
Jason Wang <jasowang at redhat.com> wrote:
> Mdev bus only supports vfio driver right now, so it doesn't implement
> match method. But in the future, we may add drivers other than vfio,
> the first driver could be virtio-mdev. This means we need to add
> device class id support in bus match method to pair the mdev device
> and mdev driver correctly.
>...
2019 Sep 17
2
[RFC v4 0/3] vhost: introduce mdev based hardware backend
...gt; b) Introduce /dev/vhost-mdev to do vhost ioctls and support
> > setting mdev device as backend;
> >
> > Now the userspace API looks like this:
> >
> > - Userspace generates a compatible mdev device;
> >
> > - Userspace opens this mdev device with VFIO API (including
> > doing IOMMU programming for this mdev device with VFIO's
> > container/group based interface);
> >
> > - Userspace opens /dev/vhost-mdev and gets vhost fd;
> >
> > - Userspace uses vhost ioctls to setup vhost (userspace should
>...
2019 Sep 17
2
[RFC v4 0/3] vhost: introduce mdev based hardware backend
...gt; b) Introduce /dev/vhost-mdev to do vhost ioctls and support
> > setting mdev device as backend;
> >
> > Now the userspace API looks like this:
> >
> > - Userspace generates a compatible mdev device;
> >
> > - Userspace opens this mdev device with VFIO API (including
> > doing IOMMU programming for this mdev device with VFIO's
> > container/group based interface);
> >
> > - Userspace opens /dev/vhost-mdev and gets vhost fd;
> >
> > - Userspace uses vhost ioctls to setup vhost (userspace should
>...
2018 Feb 14
2
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
On Wed, 14 Feb 2018 14:53:40 +0000
Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote:
> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
> VFIO_IOMMU_TYPE1 as well.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
> ---
> drivers/vfio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/...
2018 Feb 14
2
[PATCH 4/4] vfio: Allow type-1 IOMMU instantiation with a virtio-iommu
On Wed, 14 Feb 2018 14:53:40 +0000
Jean-Philippe Brucker <jean-philippe.brucker at arm.com> wrote:
> When enabling both VFIO and VIRTIO_IOMMU modules, automatically select
> VFIO_IOMMU_TYPE1 as well.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
> ---
> drivers/vfio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/...
2016 Apr 18
1
[PATCH RFC 3/3] vfio: add virtio pci quirk
...Apr 2016 12:58:28 +0300
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM
> to signal they are safe to use with an IOMMU.
>
> Without this bit, exposing the device to userspace is unsafe, so probe
> and fail VFIO initialization unless noiommu is enabled.
>
> Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
> ---
> drivers/vfio/pci/vfio_pci_private.h | 1 +
> drivers/vfio/pci/vfio_pci.c | 11 +++
> drivers/vfio/pci/vfio_pci_virtio.c | 135 +++++++++++++++++++++++++++...