RE: [PATCH v3 00/19] IOMMUFD Dirty Tracking

Shameerali Kolothum Thodi
2023-09-26T08:58:37Z

> -----Original Message-----
> From: Joao Martins [mailto:joao.m.martins@oracle.com]
> Sent: 23 September 2023 02:25
> To: iommu@lists.linux.dev
> Cc: Jason Gunthorpe <jgg@nvidia.com>; Kevin Tian <kevin.tian@intel.com>;
> Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>; Lu
> Baolu <baolu.lu@linux.intel.com>; Yi Liu <yi.l.liu@intel.com>; Yi Y Sun
> <yi.y.sun@intel.com>; Nicolin Chen <nicolinc@nvidia.com>; Joerg Roedel
> <joro@8bytes.org>; Suravee Suthikulpanit
> <suravee.suthikulpanit@amd.com>; Will Deacon <will@kernel.org>; Robin
> Murphy <robin.murphy@arm.com>; Alex Williamson
> <alex.williamson@redhat.com>; kvm@vger.kernel.org; Joao Martins
> <joao.m.martins@oracle.com>
> Subject: [PATCH v3 00/19] IOMMUFD Dirty Tracking
>
[...]
> For ARM-SMMU-v3 I've made adjustments from the RFCv2 but staged this
> into a branch[6] with all the changes but didn't include here as I can't
> test this besides compilation. Shameer, if you can pick up as chatted
> sometime ago it would be great as you have the hardware. Note that
> it depends on some patches from Nicolin for hw_info() and
> domain_alloc_user() base support coming from his nesting work.

Thanks Joao. Sure will do.

Shameer