summaryrefslogtreecommitdiff
path: root/mm/sparse-vmemmap.c
diff options
context:
space:
mode:
authorJérôme Glisse <jglisse@redhat.com>2018-04-11 02:28:38 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2018-04-11 20:28:30 +0300
commitff05c0c6bbe5043af6a1686522ed845f40ba49ee (patch)
tree9799943dde9991379fc2569182f5ba5cf7accad7 /mm/sparse-vmemmap.c
parent86586a41b8fe655e28be418a40e9bb2bb478cdd5 (diff)
downloadlinux-ff05c0c6bbe5043af6a1686522ed845f40ba49ee.tar.xz
mm/hmm: use uint64_t for HMM pfn instead of defining hmm_pfn_t to ulong
All device driver we care about are using 64bits page table entry. In order to match this and to avoid useless define convert all HMM pfn to directly use uint64_t. It is a first step on the road to allow driver to directly use pfn value return by HMM (saving memory and CPU cycles use for conversion between the two). Link: http://lkml.kernel.org/r/20180323005527.758-9-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 'mm/sparse-vmemmap.c')
0 files changed, 0 insertions, 0 deletions