powerpc/mm: Increase MAX_PHYSMEM_BITS to 128TB with SPARSEMEM_VMEMMAP config
We do this only with VMEMMAP config so that our page_to_[nid/section] etc are not impacted. Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
This commit is contained in:
parent
6aba0c84ec
commit
7d4340bb92
|
@ -6,13 +6,20 @@
|
|||
#ifdef CONFIG_SPARSEMEM
|
||||
/*
|
||||
* SECTION_SIZE_BITS 2^N: how big each section will be
|
||||
* MAX_PHYSADDR_BITS 2^N: how much physical address space we have
|
||||
* MAX_PHYSMEM_BITS 2^N: how much memory we can have in that space
|
||||
*/
|
||||
#define SECTION_SIZE_BITS 24
|
||||
|
||||
#define MAX_PHYSADDR_BITS 46
|
||||
/*
|
||||
* If we store section details in page->flags we can't increase the MAX_PHYSMEM_BITS
|
||||
* if we increase SECTIONS_WIDTH we will not store node details in page->flags and
|
||||
* page_to_nid does a page->section->node lookup
|
||||
* Hence only increase for VMEMMAP.
|
||||
*/
|
||||
#ifdef CONFIG_SPARSEMEM_VMEMMAP
|
||||
#define MAX_PHYSMEM_BITS 47
|
||||
#else
|
||||
#define MAX_PHYSMEM_BITS 46
|
||||
#endif
|
||||
|
||||
#endif /* CONFIG_SPARSEMEM */
|
||||
|
||||
|
|
Loading…
Reference in New Issue