[PATCH 2/9] mm: Add an apply_to_pfn_range interface v2

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

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On Wed, Apr 17, 2019 at 09:15:52AM +, Thomas Hellstrom wrote: > On Tue, 2019-04-16 at 10:46 -0400, Jerome Glisse wrote: > > On Sat, Apr 13, 2019 at 08:34:02AM +, Thomas Hellstrom wrote: > > > Hi, Jérôme > > > > > > On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote: > > > > On Fri,

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On Tue, 2019-04-16 at 10:46 -0400, Jerome Glisse wrote: > On Sat, Apr 13, 2019 at 08:34:02AM +, Thomas Hellstrom wrote: > > Hi, Jérôme > > > > On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote: > > > On Fri, Apr 12, 2019 at 04:04:18PM +, Thomas Hellstrom wrote: > > > > This is

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On Sat, Apr 13, 2019 at 08:34:02AM +, Thomas Hellstrom wrote: > Hi, Jérôme > > On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote: > > On Fri, Apr 12, 2019 at 04:04:18PM +, Thomas Hellstrom wrote: > > > This is basically apply_to_page_range with added functionality: > > > Allocating

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On 4/12/19 9:04 AM, 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 of the closure struct and

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

Hi, Jérôme On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote: > On Fri, Apr 12, 2019 at 04:04:18PM +, 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

Re: [PATCH 2/9] mm: Add an apply_to_pfn_range interface

On Fri, Apr 12, 2019 at 04:04:18PM +, 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

[PATCH 2/9] mm: Add an apply_to_pfn_range interface

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