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

[Mike Rapoport]

On Mon, 02 Nov 2026 11:25:18 +0800, Muchun Song <songmuchun@xxxxxxxxxxxxx> 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.
> 
> [...]

Reviewed-by: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>

-- 
Sincerely yours,
Mike.