Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" <r...@kernel.org> > > numa_cleanup_meminfo() moves blocks outside system RAM to > numa_reserved_meminfo and it uses 0 and PFN_PHYS(max_pfn) to determine > the memory boundaries. > > Replace the memory range boundaries with more portable > memblock_start_of_DRAM() and memblock_end_of_DRAM().
Can you say a bit more about why this is more portable? Is there any scenario for which (0, max_pfn) does the wrong thing?
