[PATCH 2/5] mmu_notifier: keep track of active invalidation ranges v2

From: Jérôme Glisse The mmu_notifier_invalidate_range_start() and mmu_notifier_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 inva

Re: [PATCH 2/5] mmu_notifier: keep track of active invalidation ranges

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2014 03:42 PM, j.gli...@gmail.com wrote: > From: Jérôme Glisse > > The mmu_notifier_invalidate_range_start() and > mmu_notifier_invalidate_range_end() can be considered as forming > an "atomic" section for the cpu page table update point of

[PATCH 2/5] mmu_notifier: keep track of active invalidation ranges

From: Jérôme Glisse The mmu_notifier_invalidate_range_start() and mmu_notifier_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 inva