Re: [PATCH v3 05/12] mm: hugetlb_vmemmap: unify writable vmemmap page preparation
From: Oscar Salvador (SUSE)
Date: Wed Nov 04 2026 - 05:02:54 EST
On Wed, Nov 04, 2026 at 10:35:03AM +0800, Muchun Song wrote:
> Installing a writable vmemmap page requires consuming a replacement page,
> copying the current contents into it and making the copy visible before
> publishing the new mapping. HVO currently splits this sequence between
> the page-table walker and its caller depending on the remap path.
>
> Centralize the sequence in the walker so all writable replacements follow
> the same copy-and-publish protocol. This keeps page preparation with the
> mapping update and removes path-specific handling from higher-level HVO
> code.
>
> 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