Re: [PATCH 05/12] mm: Remove remaining uses of PFN_DEV

Alistair Popple wrote: > PFN_DEV was used by callers of dax_direct_access() to figure out if the > returned PFN is associated with a page using pfn_t_has_page() or > not. However all DAX PFNs now require an assoicated ZONE_DEVICE page so can > assume a page exists. > > Other users of PFN_DEV were

Re: [PATCH 05/12] mm: Remove remaining uses of PFN_DEV

On Thu, May 29, 2025 at 04:32:06PM +1000, Alistair Popple wrote: > PFN_DEV was used by callers of dax_direct_access() to figure out if the > returned PFN is associated with a page using pfn_t_has_page() or > not. However all DAX PFNs now require an assoicated ZONE_DEVICE page so can > assume a page

[PATCH 05/12] mm: Remove remaining uses of PFN_DEV

PFN_DEV was used by callers of dax_direct_access() to figure out if the returned PFN is associated with a page using pfn_t_has_page() or not. However all DAX PFNs now require an assoicated ZONE_DEVICE page so can assume a page exists. Other users of PFN_DEV were setting it before calling vmf_inser