diff options
| author | Peter Xu <peterx@redhat.com> | 2019-01-30 13:57:57 +0800 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2019-01-30 17:31:36 +0100 |
| commit | 1a9eb9b98f0a6c8836cc4d6dcf4d5d005fb5f389 (patch) | |
| tree | 7387183863aacd8b4f5c7e31fca7c00a4670d9cf /drivers/iommu | |
| parent | 21d5d27c042d41d0ec1d138651909405d967f8af (diff) | |
| download | linux-1a9eb9b98f0a6c8836cc4d6dcf4d5d005fb5f389.tar.bz2 | |
iommu/vt-d: Remove change_pte notifier
The change_pte() interface is tailored for PFN updates, while the
other notifier invalidate_range() should be enough for Intel IOMMU
cache flushing. Actually we've done similar thing for AMD IOMMU
already in 8301da53fbc1 ("iommu/amd: Remove change_pte mmu_notifier
call-back", 2014-07-30) but the Intel IOMMU driver still have it.
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu')
| -rw-r--r-- | drivers/iommu/intel-svm.c | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/drivers/iommu/intel-svm.c b/drivers/iommu/intel-svm.c index 79add5716552..c79540deaf00 100644 --- a/drivers/iommu/intel-svm.c +++ b/drivers/iommu/intel-svm.c @@ -180,14 +180,6 @@ static void intel_flush_svm_range(struct intel_svm *svm, unsigned long address, rcu_read_unlock(); } -static void intel_change_pte(struct mmu_notifier *mn, struct mm_struct *mm, - unsigned long address, pte_t pte) -{ - struct intel_svm *svm = container_of(mn, struct intel_svm, notifier); - - intel_flush_svm_range(svm, address, 1, 1, 0); -} - /* Pages have been freed at this point */ static void intel_invalidate_range(struct mmu_notifier *mn, struct mm_struct *mm, @@ -227,7 +219,6 @@ static void intel_mm_release(struct mmu_notifier *mn, struct mm_struct *mm) static const struct mmu_notifier_ops intel_mmuops = { .release = intel_mm_release, - .change_pte = intel_change_pte, .invalidate_range = intel_invalidate_range, }; |