Re: [PATCH 04/12] mm: hugetlb_vmemmap: generalize vmemmap page allocation

From: Qi Zheng

Date: Sun Nov 01 2026 - 01:41:44 EST




On 10/20/26 7:58 PM, Muchun Song wrote:
Vmemmap page allocation is currently tied to restoring a virtual range
and assumes an empty destination list. These constraints prevent it from
being reused when pages are requested independently of a vmemmap range or
appended to an existing list.

Generalize the allocator and give it an all-or-nothing list contract so
the restore and optimization paths can share the same allocation policy.
This also allows HVO head-page allocation to fail gracefully under memory
pressure without triggering the OOM killer.

Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
---
mm/hugetlb_vmemmap.c | 40 ++++++++++++++++++----------------------
1 file changed, 18 insertions(+), 22 deletions(-)

LGTM. so:

Reviewed-by: Qi Zheng <qi.zheng@xxxxxxxxx>

Thanks,
Qi