diff options
| author | Lu Baolu <baolu.lu@linux.intel.com> | 2019-04-12 12:26:13 +0800 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2019-04-12 13:02:42 +0200 |
| commit | f7b0c4ce8cb3c09cb3cbfc0c663268bf99e5fa9c (patch) | |
| tree | 4817c10480458ebb352f30cc5158c3a235c4bfa2 /drivers/iommu/qcom_iommu.c | |
| parent | be068fa236c3d697c77f02f3dc9cd7afeb0538a6 (diff) | |
iommu/vt-d: Flush IOTLB for untrusted device in time
By default, for performance consideration, Intel IOMMU
driver won't flush IOTLB immediately after a buffer is
unmapped. It schedules a thread and flushes IOTLB in a
batched mode. This isn't suitable for untrusted device
since it still can access the memory even if it isn't
supposed to do so.
Cc: Ashok Raj <ashok.raj@intel.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
Tested-by: Xu Pengfei <pengfei.xu@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@intel.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/qcom_iommu.c')
0 files changed, 0 insertions, 0 deletions