Re: [PATCH 02/15] mmu_notifier: keep track of active invalidation ranges v4

2015-09-01 Thread Jerome Glisse
On Mon, Aug 31, 2015 at 08:27:17PM -0700, Mark Hairgrove wrote: > On Thu, 13 Aug 2015, Jérôme Glisse wrote: [...] Will fix syntax. [...] > > +/* mmu_notifier_range_wait_valid() - wait for a range to have no conflict > > with > > + * active invalidation. > > + * > > + * @mm: The mm struct. > >

Re: [PATCH 02/15] mmu_notifier: keep track of active invalidation ranges v4

2015-08-31 Thread Mark Hairgrove
On Thu, 13 Aug 2015, Jérôme Glisse wrote: > The invalidate_range_start() and invalidate_range_end() can be > considered as forming an "atomic" section for the cpu page table > update point of view. Between this two function the cpu page > table content is unreliable for the address range being >