[PATCH v3 6/6] Revert "arch: introduce set_direct_map_valid_noflush()"

[David Hildenbrand (Arm)]

On 9/3/26 11:28, Mike Rapoport (Microsoft) wrote:
> Commit 0c6378a71574 ("arch: introduce set_direct_map_valid_noflush()")
> added set_direct_map_valid_noflush() to allow updating the direct map
> for a physically contiguous range in execmem.
> 
> As Brendan recently pointed out [1], this API is confusing because on
> arm64 it means that is sets VALID bit in ptes, while on other
> architectures it is an analog of set_direct_map_default_noflush().
> 
> The only user of set_direct_map_valid_noflush() was execmem's ROX cache
> freeing path and it was switched to utilize VM_FLUSH_RESET_PERMS for
> resetting permissions of the direct map alias.
> 
> With the last user gone and with set_direct_map_{invalid,default}_noflush()
> accepting number of pages as a parameter, set_direct_map_valid_noflush()
> become a copy of set_memory_valid() on arm64 and a duplicate of
> set_direct_map_{invalid,default}_noflush() on other architecture, it is
> safe to remove set_direct_map_valid_noflush().
> 
> Also drop a stale comment in arm64::__kernel_map_pages() that Linus
> bothered to add when merging changes containing set_direct_map_valid_noflush()
> to his tree.
> 
> This reverts commit 0c6378a71574daa6cd1534ad42a956e3262756c7.
> 
> [1] https://lore.kernel.org/all/DJ69RCVRBO0Y.3JCYSW50IC4RC@linux.dev
> 
> Reviewed-by: Brendan Jackman <brendan.jackman at linux.dev>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt at kernel.org>
> ---

Thanks!

Acked-by: David Hildenbrand (Arm) <david at kernel.org>

-- 
Cheers,

David