On Thu, Aug 06, 2020 at 09:29:36AM +0200, David Hildenbrand wrote: >On 05.08.20 23:49, Wei Yang wrote: >> On Fri, Jul 03, 2020 at 11:18:28AM +0800, Wei Yang wrote: >>> There are two code path which invoke __populate_section_memmap() >>> >>> * sparse_init_nid() >>> * sparse_add_section() >>> >>> For both case, we are sure the memory range is sub-section aligned. >>> >>> * we pass PAGES_PER_SECTION to sparse_init_nid() >>> * we check range by check_pfn_span() before calling >>> sparse_add_section() >>> >>> Also, the counterpart of __populate_section_memmap(), we don't do such >>> calculation and check since the range is checked by check_pfn_span() in >>> __remove_pages(). >>> >>> Clear the calculation and check to keep it simple and comply with its >>> counterpart. >>> >>> Signed-off-by: Wei Yang <richard.weiyang@xxxxxxxxxxxxxxxxx> >>> >> >> Hi, Andrew, >> >> Is this one picked up? > >I can spot it in -next via the -mm tree: > >https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=68ad9becb23be14622e39ed36e5b0621a90a41d9 > Thanks ;-) Next time I would refer to this repo first. > >-- >Thanks, > >David / dhildenb -- Wei Yang Help you, Help me
