summaryrefslogtreecommitdiffstats
path: root/scripts/Makefile.modbuiltin
diff options
context:
space:
mode:
authorJérôme Glisse <jglisse@redhat.com>2018-04-10 16:28:42 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2018-04-11 10:28:30 -0700
commit855ce7d2525c97cf706ad82a419f0c2d632b9481 (patch)
tree4c7cb4c0d14450792fdf512b5eb8e0832080ec8e /scripts/Makefile.modbuiltin
parentff05c0c6bbe5043af6a1686522ed845f40ba49ee (diff)
downloadtalos-op-linux-855ce7d2525c97cf706ad82a419f0c2d632b9481.tar.gz
talos-op-linux-855ce7d2525c97cf706ad82a419f0c2d632b9481.zip
mm/hmm: cleanup special vma handling (VM_SPECIAL)
Special vma (one with any of the VM_SPECIAL flags) can not be access by device because there is no consistent model across device drivers on those vma and their backing memory. This patch directly use hmm_range struct for hmm_pfns_special() argument as it is always affecting the whole vma and thus the whole range. It also make behavior consistent after this patch both hmm_vma_fault() and hmm_vma_get_pfns() returns -EINVAL when facing such vma. Previously hmm_vma_fault() returned 0 and hmm_vma_get_pfns() return -EINVAL but both were filling the HMM pfn array with special entry. Link: http://lkml.kernel.org/r/20180323005527.758-10-jglisse@redhat.com Signed-off-by: Jérôme Glisse <jglisse@redhat.com> Reviewed-by: John Hubbard <jhubbard@nvidia.com> Cc: Evgeny Baskakov <ebaskakov@nvidia.com> Cc: Ralph Campbell <rcampbell@nvidia.com> Cc: Mark Hairgrove <mhairgrove@nvidia.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts/Makefile.modbuiltin')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud