On Thu, May 29, 2025 at 07:07:56PM +0530, Aneesh Kumar K.V (Arm) wrote: > Signed-off-by: Aneesh Kumar K.V (Arm) <aneesh.kumar@xxxxxxxxxx> > --- > drivers/iommu/iommufd/iommufd_private.h | 3 + > drivers/iommu/iommufd/main.c | 5 ++ > drivers/iommu/iommufd/viommu.c | 78 +++++++++++++++++++++++++ > include/uapi/linux/iommufd.h | 15 +++++ > 4 files changed, 101 insertions(+) > > diff --git a/drivers/iommu/iommufd/iommufd_private.h b/drivers/iommu/iommufd/iommufd_private.h > index 80e8c76d25f2..a323e8b18125 100644 > --- a/drivers/iommu/iommufd/iommufd_private.h > +++ b/drivers/iommu/iommufd/iommufd_private.h > @@ -606,6 +606,8 @@ int iommufd_viommu_alloc_ioctl(struct iommufd_ucmd *ucmd); > void iommufd_viommu_destroy(struct iommufd_object *obj); > int iommufd_vdevice_alloc_ioctl(struct iommufd_ucmd *ucmd); > void iommufd_vdevice_destroy(struct iommufd_object *obj); > +int iommufd_vdevice_tsm_bind_ioctl(struct iommufd_ucmd *ucmd); > +int iommufd_vdevice_tsm_unbind_ioctl(struct iommufd_ucmd *ucmd); Hello: I recently have another concern about the vdevice tsm bind/unbind API. And need your inputs. According to this: https://lore.kernel.org/all/aC9QPoEUw_nLHhV4@xxxxxxxxxx/ Sean illustrates the memory in-place conversion, that the memory owner - gmemfd should own & control the memory shareability) and the conversion. I.e. For in-place conversion, KVM_SET_MEMORY_ATTRIBUTES should be disabled. Private/shared MMIO must be of in-place conversion, similarly it's the MMIO owner should be responsible for MMIO shareability, maybe adding some new ioctls like MMIO_CONVERT_SHARED/PRIVATE.
