Re: [PATCH v1 15/16] mm: rename zap_vma_ptes() to zap_special_vma_range()

"David Hildenbrand (Arm)" <[email protected]> Wed, 11 Mar 2026 09:20:53 +0100

Newsgroups	org.kernel.vger.linux-sgx,org.freedesktop.lists.dri-devel,org.freedesktop.lists.intel-gfx,org.kernel.vger.bpf,org.kernel.vger.kvm,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-rdma,org.kernel.vger.linux-s390,org.kernel.vger.netdev,org.kernel.vger.rust-for-linux,org.kvack.linux-mm,org.ozlabs.lists.linuxppc-dev
Message-ID	<[email protected]>

On 3/6/26 13:41, Lorenzo Stoakes (Oracle) wrote:
> On Fri, Feb 27, 2026 at 09:08:46PM +0100, David Hildenbrand (Arm) wrote:
>> zap_vma_ptes() is the only zapping function we export to modules.
>>
>> It's essentially a wrapper around zap_vma_range(), however, with some
>> safety checks:
>> * That the passed range fits fully into the VMA
>> * That it's only used for VM_PFNMAP
>>
>> We might want to support VM_MIXEDMAP soon as well, so use the
> 
> I think you should say we _are_ going to since patch 16/16 does that :)

Heh, had that patch separate first before I decided to support
VM_MIXEDMAP in the same series.

@Andrew, can you fix that up? Thanks!

"We will add support for VM_MIXEDMAP next, so ..."

-- 
Cheers,

David