Re: [RFC PATCH RESEND 2/3] mm: Add an apply_to_pfn_range interface

2019-03-21 Thread Jerome Glisse
On Thu, Mar 21, 2019 at 07:59:35PM +, Thomas Hellstrom wrote: > On Thu, 2019-03-21 at 09:52 -0400, Jerome Glisse wrote: > > On Thu, Mar 21, 2019 at 01:22:35PM +, Thomas Hellstrom wrote: > > > This is basically apply_to_page_range with added functionality: > > > Allocating missing parts of t

Re: [RFC PATCH RESEND 2/3] mm: Add an apply_to_pfn_range interface

2019-03-21 Thread Thomas Hellstrom
On Thu, 2019-03-21 at 09:52 -0400, Jerome Glisse wrote: > On Thu, Mar 21, 2019 at 01:22:35PM +, Thomas Hellstrom wrote: > > This is basically apply_to_page_range with added functionality: > > Allocating missing parts of the page table becomes optional, which > > means that the function can be g

Re: [RFC PATCH RESEND 2/3] mm: Add an apply_to_pfn_range interface

2019-03-21 Thread Jerome Glisse
On Thu, Mar 21, 2019 at 01:22:35PM +, Thomas Hellstrom wrote: > This is basically apply_to_page_range with added functionality: > Allocating missing parts of the page table becomes optional, which > means that the function can be guaranteed not to error if allocation > is disabled. Also passing

[RFC PATCH RESEND 2/3] mm: Add an apply_to_pfn_range interface

2019-03-21 Thread Thomas Hellstrom
This is basically apply_to_page_range with added functionality: Allocating missing parts of the page table becomes optional, which means that the function can be guaranteed not to error if allocation is disabled. Also passing of the closure struct and callback function becomes different and more in