Lines Matching refs:iommu_domain
11 * 2) An iommu_domain
25 * If the domains_itree includes the PFN's index then an iommu_domain is storing
31 * means removing an iommu_domain or releasing a in-kernel access will not fail
33 * PFNs in the xarray even though they are also being stored in an iommu_domain.
35 * While the iopt_pages can use an iommu_domain as storage, it does not have an
221 static void iommu_unmap_nofail(struct iommu_domain *domain, unsigned long iova,
238 struct iommu_domain *domain,
376 struct iommu_domain *domain,
402 static struct page **raw_pages_from_domain(struct iommu_domain *domain,
427 struct iommu_domain *domain,
447 static int batch_iommu_map_small(struct iommu_domain *domain,
475 static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
930 * - The iommu_domain under an area
1198 struct iopt_pages *pages, struct iommu_domain *domain,
1259 struct iommu_domain *domain,
1311 struct iommu_domain *domain,
1326 void iopt_area_unmap_domain(struct iopt_area *area, struct iommu_domain *domain)
1343 struct iommu_domain *domain)
1357 int iopt_area_fill_domain(struct iopt_area *area, struct iommu_domain *domain)
1412 struct iommu_domain *domain;
1495 struct iommu_domain *domain;
1740 * do every scenario and is fully consistent with what an iommu_domain would