Re: [PATCH v3 1/2] x86/devmem: Remove duplicate range_is_allowed() definition

[Dave Hansen]

On 4/17/25 12:12, Dan Williams wrote:
> The only thing preventing a common implementation is that
> phys_mem_access_prot_allowed() expects the range check to exit
> immediately when PAT is disabled [2]. I.e. there is no cache conflict to
> manage in that case. This cleanup was noticed on the path to
> considering changing range_is_allowed() policy to blanket deny /dev/mem
> for private (confidential computing) memory.

Yay, removing duplicated code!

Acked-by: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>