On Wed, 23 Oct 2024 17:24:38 +0100 Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx> wrote: > > ... > > Existing mechanism for performing a walk which also installs page table > entries if necessary are heavily duplicated throughout the kernel, How complicated is it to migrate those to use this? > ... > > We explicitly do not allow the existing page walk API to expose this > feature as it is dangerous and intended for internal mm use only. Therefore > we provide a new walk_page_range_mm() function exposed only to > mm/internal.h. > Is this decision compatible with the above migrations?
