Searched refs:IOVA (Results 1 – 6 of 6) sorted by relevance
9 - dma-window : IOVA start address and length.19 dma-window = <0 0x40000000>; /* IOVA start & length */
20 Description: /sys/kernel/iommu_groups/reserved_regions list IOVA25 the base IOVA, the second is the end IOVA and the third
36 of user space memory into ranges of I/O Virtual Address (IOVA).39 container it copies an IOVA map to a list of iommu_domains held within it.52 The IOAS has a list of HWPT_PAGINGs that share the same IOVA mapping and300 would do. The access object will then allow converting IOVA ranges into struct301 page * lists, or doing direct read/write to an IOVA.303 iommufd_ioas serves as the metadata datastructure to manage how IOVA ranges are306 - struct io_pagetable holding the IOVA map307 - struct iopt_area's representing populated portions of IOVA323 list of iommu_domains that mirror the IOVA to PFN map.
478 Part Ie - IOVA-based DMA mappings491 Is used to try to allocate IOVA space for mapping operation. If it returns500 Can be used by the driver to check if the IOVA-based API is used after a509 Is used to link ranges to the IOVA previously allocated. The start of all520 Must be called to sync the IOMMU page tables for IOVA-range mapped by one or524 IOVA freed by calling:532 Alternatively drivers can dynamically manage the IOVA space by unmapping547 is used to free the IOVA space. All regions must have been unmapped using
352 IOVA, enumerator
2669 iommu.forcedac= [ARM64,X86,EARLY] Control IOVA allocation for PCI devices.