Re: [PATCH v1 05/11] mm/sparse-vmemmap: add a pgmap argument to section activation

On 5/6/21 12:14 AM, Dan Williams wrote: > On Wed, May 5, 2021 at 3:38 PM Joao Martins wrote: >> >> >> >> On 5/5/21 11:34 PM, Dan Williams wrote: >>> On Thu, Mar 25, 2021 at 4:10 PM Joao Martins >>> wrote: @altmap is stored in a dev_pagemap, but it will be repurposed for

Re: [PATCH v1 05/11] mm/sparse-vmemmap: add a pgmap argument to section activation

On Wed, May 5, 2021 at 3:38 PM Joao Martins wrote: > > > > On 5/5/21 11:34 PM, Dan Williams wrote: > > On Thu, Mar 25, 2021 at 4:10 PM Joao Martins > > wrote: > >> > >> @altmap is stored in a dev_pagemap, but it will be repurposed for > >> hotplug memory for storing the memmap in the hotplugged

Re: [PATCH v1 05/11] mm/sparse-vmemmap: add a pgmap argument to section activation

On 5/5/21 11:34 PM, Dan Williams wrote: > On Thu, Mar 25, 2021 at 4:10 PM Joao Martins > wrote: >> >> @altmap is stored in a dev_pagemap, but it will be repurposed for >> hotplug memory for storing the memmap in the hotplugged memory[*] and >> reusing the altmap infrastructure to that end.

Re: [PATCH v1 05/11] mm/sparse-vmemmap: add a pgmap argument to section activation

On Thu, Mar 25, 2021 at 4:10 PM Joao Martins wrote: > > @altmap is stored in a dev_pagemap, but it will be repurposed for > hotplug memory for storing the memmap in the hotplugged memory[*] and > reusing the altmap infrastructure to that end. This is to say that > altmap can't be replaced with a