mm/hmm: do not differentiate between empty entry or missing directory
There is no point in differentiating between a range for which there is not even a directory (and thus entries) and empty entry (pte_none() or pmd_none() returns true). Simply drop the distinction ie remove HMM_PFN_EMPTY flag and merge now duplicate hmm_vma_walk_hole() and hmm_vma_walk_clear() functions. Link: http://lkml.kernel.org/r/20180323005527.758-11-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>
This commit is contained in:

committed by
Linus Torvalds

parent
855ce7d252
commit
5504ed2969
@@ -84,7 +84,6 @@ struct hmm;
|
||||
* HMM_PFN_VALID: pfn is valid. It has, at least, read permission.
|
||||
* HMM_PFN_WRITE: CPU page table has write permission set
|
||||
* HMM_PFN_ERROR: corresponding CPU page table entry points to poisoned memory
|
||||
* HMM_PFN_EMPTY: corresponding CPU page table entry is pte_none()
|
||||
* HMM_PFN_SPECIAL: corresponding CPU page table entry is special; i.e., the
|
||||
* result of vm_insert_pfn() or vm_insert_page(). Therefore, it should not
|
||||
* be mirrored by a device, because the entry will never have HMM_PFN_VALID
|
||||
@@ -94,10 +93,9 @@ struct hmm;
|
||||
#define HMM_PFN_VALID (1 << 0)
|
||||
#define HMM_PFN_WRITE (1 << 1)
|
||||
#define HMM_PFN_ERROR (1 << 2)
|
||||
#define HMM_PFN_EMPTY (1 << 3)
|
||||
#define HMM_PFN_SPECIAL (1 << 4)
|
||||
#define HMM_PFN_DEVICE_UNADDRESSABLE (1 << 5)
|
||||
#define HMM_PFN_SHIFT 6
|
||||
#define HMM_PFN_SPECIAL (1 << 3)
|
||||
#define HMM_PFN_DEVICE_UNADDRESSABLE (1 << 4)
|
||||
#define HMM_PFN_SHIFT 5
|
||||
|
||||
/*
|
||||
* hmm_pfn_to_page() - return struct page pointed to by a valid HMM pfn
|
||||
|
Reference in New Issue
Block a user