On 19/02/2019 03:44, Liang, Kan wrote: > > > On 2/18/2019 9:19 AM, Steven Price wrote: >> On 18/02/2019 11:31, Peter Zijlstra wrote: >>> On Fri, Feb 15, 2019 at 05:02:24PM +0000, Steven Price wrote: >>>> From: James Morse <james.morse@xxxxxxx> >>>> >>>> Exposing the pud/pgd levels of the page tables to walk_page_range() >>>> means >>>> we may come across the exotic large mappings that come with large areas >>>> of contiguous memory (such as the kernel's linear map). >>>> >>>> For architectures that don't provide p?d_large() macros, provided a >>>> does nothing default. >>> >>> Kan was going to fix that for all archs I think.. >> > > Yes, I'm still working on a generic function to retrieve page size. > The generic p?d_large() issue has been fixed. However, I found that the > pgd_page() is not generic either. I'm still working on it. > I will update you on the other thread when all issues are fixed. > > > >> The latest series I can find from Kan is still x86 specific. I'm happy >> to rebase onto something else if Kan has an implementation already >> (please point me in the right direction). Otherwise Kan is obviously >> free to base on these changes. >> > > My implementation is similar as yours. I'm happy to re-base on your > changes. > > Could you please also add a generic p4d_large()? Sure, I'll include that in the next posting. Thanks, Steve
