Re: [PATCH 1/2] mm,sparse: Fix deactivate_section for early sections

2019-07-18 Thread David Hildenbrand
On 15.07.19 10:15, Oscar Salvador wrote: > deactivate_section checks whether a section is early or not > in order to either call free_map_bootmem() or depopulate_section_memmap(). > Being the former for sections added at boot time, and the latter for > sections hotplugged. > > The problem is that

Re: [PATCH 1/2] mm,sparse: Fix deactivate_section for early sections

2019-07-15 Thread Dan Williams
On Mon, Jul 15, 2019 at 1:16 AM Oscar Salvador wrote: > > deactivate_section checks whether a section is early or not > in order to either call free_map_bootmem() or depopulate_section_memmap(). > Being the former for sections added at boot time, and the latter for > sections hotplugged. > > The p

Re: [PATCH 1/2] mm,sparse: Fix deactivate_section for early sections

2019-07-15 Thread Aneesh Kumar K.V
Oscar Salvador writes: > deactivate_section checks whether a section is early or not > in order to either call free_map_bootmem() or depopulate_section_memmap(). > Being the former for sections added at boot time, and the latter for > sections hotplugged. > > The problem is that we zero section_m

[PATCH 1/2] mm,sparse: Fix deactivate_section for early sections

2019-07-15 Thread Oscar Salvador
deactivate_section checks whether a section is early or not in order to either call free_map_bootmem() or depopulate_section_memmap(). Being the former for sections added at boot time, and the latter for sections hotplugged. The problem is that we zero section_mem_map, so the last early_section()