Thread (113 messages) 113 messages, 13 authors, 2018-09-13

[PATCH v2 03/40] iommu/sva: Manage process address spaces

From: Jacob Pan <hidden>
Date: 2018-09-05 18:16:38
Also in: kvm, linux-acpi, linux-devicetree, linux-iommu, linux-mm, linux-pci

On Wed, 5 Sep 2018 14:14:12 +0200
Auger Eric [off-list ref] wrote:
quoted
+ *
+ * On Arm and AMD IOMMUs, entry 0 of the PASID table can be used
to hold
+ * non-PASID translations. In this case PASID 0 is reserved and
entry 0 points
+ * to the io_pgtable base. On Intel IOMMU, the io_pgtable base
would be held in
+ * the device table and PASID 0 would be available to the
allocator.
+ */  
very nice explanation
With the new Vt-d 3.0 spec., 2nd level IO page table base is no longer
held in the device context table. Instead it is held in the PASID table
entry pointed by the RID_PASID field in the device context entry. If
RID_PASID = 0, then it is the same as ARM and AMD IOMMUs.
You can refer to ch3.4.3 of the VT-d spec.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help