diff options
author | Jérôme Glisse <jglisse@redhat.com> | 2018-12-11 13:03:42 -0500 |
---|---|---|
committer | Jérôme Glisse <jglisse@redhat.com> | 2019-04-08 11:46:58 -0400 |
commit | f782e8bdf0661209ca23e5371e258d37d823eb8d (patch) | |
tree | d74cb6dd21dd5f56be26d70cf3b2f81ea3adf6eb | |
parent | 53f71f3dc19cc24ba8d1b08c10443e3914a1fcb3 (diff) |
mm/hmm: do not erase snapshot when a range is invalidated
Users of HMM might be using the snapshot information to do
preparatory step like dma mapping pages to a device before
checking for invalidation through hmm_vma_range_done() so
do not erase that information and assume users will do the
right thing.
Signed-off-by: Jérôme Glisse <jglisse@redhat.com>
Reviewed-by: Ralph Campbell <rcampbell@nvidia.com>
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>
-rw-r--r-- | mm/hmm.c | 6 |
1 files changed, 0 insertions, 6 deletions
@@ -174,16 +174,10 @@ static int hmm_invalidate_range(struct hmm *hmm, bool device, spin_lock(&hmm->lock); list_for_each_entry(range, &hmm->ranges, list) { - unsigned long addr, idx, npages; - if (update->end < range->start || update->start >= range->end) continue; range->valid = false; - addr = max(update->start, range->start); - idx = (addr - range->start) >> PAGE_SHIFT; - npages = (min(range->end, update->end) - addr) >> PAGE_SHIFT; - memset(&range->pfns[idx], 0, sizeof(*range->pfns) * npages); } spin_unlock(&hmm->lock); |