Re: [PATCH v6 0/2] mm/sparse-vmemmap: flush_cache_vmap() after hotplugging vmemmap

[Paul Walmsley]

On Mon, 13 Jul 2026, Vivian Wang wrote:

> Patch 1 is a bit of clean up that fixes the compilation error with patch
> 2, since VMEMMAP_{START,END} is not defined when MMU=n.
> 
> The mark_new_valid_map() thing doesn't do anything useful on MMU=n
> anyway, and the new_valid_maps_cpus_check code is only used on 64BIT, so
> I just made it all of it conditional on 64BIT && MMU. I hope this is
> acceptable.

Thanks, queued for v7.2-rc.


- Paul