RE: [PATCH v2 4/5] vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Liu, Yi L" <yi.l.liu@xxxxxxxxx>, "alex.williamson@xxxxxxxxxx" <alex.williamson@xxxxxxxxxx>, "jgg@xxxxxxxxxx" <jgg@xxxxxxxxxx>
Subject: RE: [PATCH v2 4/5] vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 17 Mar 2023 01:05:55 +0000
Accept-language: en-US
Cc: "joro@xxxxxxxxxx" <joro@xxxxxxxxxx>, "robin.murphy@xxxxxxx" <robin.murphy@xxxxxxx>, "cohuck@xxxxxxxxxx" <cohuck@xxxxxxxxxx>, "eric.auger@xxxxxxxxxx" <eric.auger@xxxxxxxxxx>, "nicolinc@xxxxxxxxxx" <nicolinc@xxxxxxxxxx>, "kvm@xxxxxxxxxxxxxxx" <kvm@xxxxxxxxxxxxxxx>, "mjrosato@xxxxxxxxxxxxx" <mjrosato@xxxxxxxxxxxxx>, "chao.p.peng@xxxxxxxxxxxxxxx" <chao.p.peng@xxxxxxxxxxxxxxx>, "yi.y.sun@xxxxxxxxxxxxxxx" <yi.y.sun@xxxxxxxxxxxxxxx>, "peterx@xxxxxxxxxx" <peterx@xxxxxxxxxx>, "jasowang@xxxxxxxxxx" <jasowang@xxxxxxxxxx>, "shameerali.kolothum.thodi@xxxxxxxxxx" <shameerali.kolothum.thodi@xxxxxxxxxx>, "lulu@xxxxxxxxxx" <lulu@xxxxxxxxxx>, "suravee.suthikulpanit@xxxxxxx" <suravee.suthikulpanit@xxxxxxx>, "intel-gvt-dev@xxxxxxxxxxxxxxxxxxxxx" <intel-gvt-dev@xxxxxxxxxxxxxxxxxxxxx>, "intel-gfx@xxxxxxxxxxxxxxxxxxxxx" <intel-gfx@xxxxxxxxxxxxxxxxxxxxx>, "linux-s390@xxxxxxxxxxxxxxx" <linux-s390@xxxxxxxxxxxxxxx>, "Hao, Xudong" <xudong.hao@xxxxxxxxx>, "Zhao, Yan Y" <yan.y.zhao@xxxxxxxxx>, "Xu, Terrence" <terrence.xu@xxxxxxxxx>
In-reply-to: <20230316121526.5644-5-yi.l.liu@intel.com>
References: <20230316121526.5644-1-yi.l.liu@intel.com> <20230316121526.5644-5-yi.l.liu@intel.com>
Thread-index: AQHZWAEK+Y1lHM/oqEGUWYXqsDaat67+KSkQ
Thread-topic: [PATCH v2 4/5] vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers

> From: Liu, Yi L <yi.l.liu@xxxxxxxxx>
> Sent: Thursday, March 16, 2023 8:15 PM
> 
> This harmonizes the no-DMA devices (the vfio-mdev sample drivers) with
> the emulated devices (gvt-g, vfio-ap etc.). It makes it easier to add
> BIND_IOMMUFD user interface which requires to return an iommufd ID to
> represent the device/iommufd bond.
> 
> Reviewed-by: Jason Gunthorpe <jgg@xxxxxxxxxx>
> Signed-off-by: Yi Liu <yi.l.liu@xxxxxxxxx>

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- [PATCH v2 0/5] vfio: Make emulated devices prepared for vfio device cdev
  - From: Yi Liu
- [PATCH v2 4/5] vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers
  - From: Yi Liu

Prev by Date: RE: [PATCH v2 2/5] vfio-iommufd: No need to record iommufd_ctx in vfio_device
Next by Date: RE: [PATCH v2 5/5] vfio: Check the presence for iommufd callbacks in __vfio_register_dev()
Previous by thread: [PATCH v2 4/5] vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers
Next by thread: RE: [PATCH v2 0/5] vfio: Make emulated devices prepared for vfio device cdev
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite Info] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Linux Media] [Device Mapper]