Re: [PATCH v3 10/12] mm: hugetlb_vmemmap: make vmemmap restoration folio-oriented

From: Oscar Salvador (SUSE)

Date: Wed Nov 04 2026 - 08:12:45 EST


On Wed, Nov 04, 2026 at 10:35:08AM +0800, Muchun Song wrote:
> Like optimization, vmemmap restoration operates on one folio at a time,
> but the current interface exposes a raw address range and requires the
> HugeTLB caller to prepare part of the operation. This splits the common
> mechanism across layers and obscures its natural unit of work.
>
> Make the folio the unit of vmemmap restoration and move the common
> mechanics behind a folio-oriented interface. This keeps HugeTLB-specific
> eligibility and state in the caller and gives both directions of HVO
> consistent folio-level interfaces.
>
> No functional change intended.
>
> Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
> Reviewed-by: Lance Yang <lance.yang@xxxxxxxxx>
> Reviewed-by: Qi Zheng <qi.zheng@xxxxxxxxx>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>

Reviewed-by: Oscar Salvador <osalvador@xxxxxxx>



--
Oscar Salvador
SUSE Labs