On 5/26/2026 11:33 PM, Lorenzo Stoakes wrote:

Allow me to be mildly pedantic (sorry :)

One thing I'd like to highlight here is that remap_pfn_range() is, in the long
run, deprecated.

mmap_prepare callbacks will indicate a PFN remap mmap_action, which will do the
heavy lifting (see [0]).

Thanks, I missed that mmap_action_remap() may also reach the same common 
PFN remap
path.

So perhaps worth referring to 'PFN remapping' or something?

(Since we already have mmap_prepare() in use, it's also kinda inaccurate to
say remap_pfn_range() :)

Agreed, describing this as remap_pfn_range()support is indeed 
inaccurate. I'll reword it.

[0]: https://www.kernel.org/doc/html/next/filesystems/mmap_prepare.html

Sorry, this is pretty nitpicky :)

Not at all, this is really helpful.

Cheers, Lorenzo

-- 
Yin Tirui