Re: [PATCH v3 5/5] mm/sparse-vmemmap: drop @pgmap from vmemmap population APIs
From: Oscar Salvador (SUSE)
Date: Mon Nov 09 2026 - 04:33:17 EST
On Sat, Nov 07, 2026 at 12:31:22PM +0800, Muchun Song wrote:
> The vmemmap population and memory hotplug paths no longer need @pgmap
> to decide whether a mapping can be optimized. That state is now carried
> in mem_section, and the architecture-specific population code can make
> the remaining decisions internally.
>
> Drop the @pgmap parameter from the vmemmap population helpers and the
> related memory hotplug interfaces, and remove the remaining
> dev_pagemap-specific coupling from those call chains.
>
> Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
Reviewed-by: Oscar Salvador (SUSE) <osalvador@xxxxxxxxxx>
--
Oscar Salvador
SUSE Labs