Message	SHA1
iommu/vt-d: Expose struct svm_dev_ops without CONFIG_INTEL_IOMMU_SVM ... The point in providing an inline version of intel_svm_bind_mm() which just returns -ENOSYS is that people are supposed to be able to *use* it and just see that it fails. So we need to let them have a definition of struct svm_dev_ops (and the flags) too. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> David Woodhouse   commited 2015-10-27 08:36:08 +09:00	da4689c026
iommu/vt-d: Implement SVM_FLAG_SUPERVISOR_MODE for kernel access ... This is only usable for the static 1:1 mapping of physical memory. Any access to vmalloc or module regions will require some way of doing an IOTLB flush. It's theoretically possible to hook into the tlb_flush_kernel_range() function, but that seems like overkill — most of the addresses accessed through a kernel PASID *will* be in the 1:1 mapping. If we really need to allow access to more interesting kernel regions, then the answer will probably be an explicit IOTLB flush call after use, akin to the DMA API's unmap function. In fact, it might be worth introducing that sooner rather than later, and making it just BUG() if the address isn't in the static 1:1 mapping. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> David Woodhouse   commited 2015-10-15 15:52:21 +01:00	5cec753709
iommu/vt-d: Implement SVM_FLAG_PRIVATE_PASID to allocate unique PASIDs ... Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> David Woodhouse   commited 2015-10-15 15:35:32 +01:00	569e4f7782
iommu/vt-d: Add callback to device driver on page faults ... Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> David Woodhouse   commited 2015-10-15 15:35:28 +01:00	0204a49609
iommu/vt-d: Add basic SVM PASID support ... This provides basic PASID support for endpoint devices, tested with a version of the i915 driver. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> David Woodhouse   commited 2015-10-15 12:55:45 +01:00	2f26e0a9c9