Re: [PATCH 05/12] mm: hugetlb_vmemmap: unify writable vmemmap page preparation

[Lance Yang]

On Tue, Oct 20, 2026 at 07:58:17PM +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>
>---

Was wondering if moving the copy into the walker could lose the optimized
flag, but it's already set before the walk, so it gets copied too :D

Looks good to me1

Reviewed-by: Lance Yang <lance.yang@xxxxxxxxx>