Hi Robin, > -----Original Message----- > From: Robin Murphy [mailto:[email protected]] > Sent: Thursday, March 09, 2017 7:51 PM > To: [email protected] > Cc: [email protected]; [email protected]; > [email protected]; Gabriele Paoloni; John Garry; Shameerali Kolothum > Thodi > Subject: [PATCH 3/3] iommu/dma: Handle IOMMU API reserved regions > > Now that it's simple to discover the necessary reservations for a given > device/IOMMU combination, let's wire up the appropriate handling. Basic > reserved regions and direct-mapped regions are obvious enough to > handle; hardware MSI regions we can handle by pre-populating the > appropriate msi_pages in the cookie. That way, irqchip drivers which > normally assume MSIs to require mapping at the IOMMU can keep working > without having to special-case their iommu_dma_map_msi_msg() hook, or > indeed be aware at all of integration quirks preventing the IOMMU > translating certain addresses.
Many thanks for this. This will help us to avoid the ugly ITS quirk to support the D03/D05. I will go through this. Cheers, Thanks. > Signed-off-by: Robin Murphy <[email protected]> > --- > drivers/iommu/dma-iommu.c | 65 > +++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 65 insertions(+) > > diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c > index 1e0983488a8d..1082ebf8a415 100644 > --- a/drivers/iommu/dma-iommu.c > +++ b/drivers/iommu/dma-iommu.c > @@ -167,6 +167,69 @@ void iommu_put_dma_cookie(struct iommu_domain > *domain) } EXPORT_SYMBOL(iommu_put_dma_cookie); [...] _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
