Re: [PATCH v8 00/20] Convert x86 & arm64 to use generic page walk

2019-04-17 Thread Steven Price
On 12/04/2019 15:44, Dave Hansen wrote: > On 4/10/19 7:56 AM, Steven Price wrote: >> Gentle ping: who can take this? Is there anything blocking this series? > > First of all, I really appreciate that you tried this. Every open-coded > page walk has a set of common pitfalls, but is pretty

Re: [PATCH v8 00/20] Convert x86 & arm64 to use generic page walk

2019-04-12 Thread Dave Hansen
On 4/10/19 7:56 AM, Steven Price wrote: > Gentle ping: who can take this? Is there anything blocking this series? First of all, I really appreciate that you tried this. Every open-coded page walk has a set of common pitfalls, but is pretty unbounded in what kinds of bugs it can contain. I think

Re: [PATCH v8 00/20] Convert x86 & arm64 to use generic page walk

2019-04-10 Thread Steven Price
Hi all, Gentle ping: who can take this? Is there anything blocking this series? Thanks, Steve On 03/04/2019 15:16, Steven Price wrote: > Most architectures current have a debugfs file for dumping the kernel > page tables. Currently each architecture has to implement custom > functions for

[PATCH v8 00/20] Convert x86 & arm64 to use generic page walk

2019-04-03 Thread Steven Price
Most architectures current have a debugfs file for dumping the kernel page tables. Currently each architecture has to implement custom functions for walking the page tables because the generic walk_page_range() function is unable to walk the page tables used by the kernel. This series extends the