On Sun, Dec 28, 2014 at 08:46:42AM +, Haggai Eran wrote:
>
> On Dec 26, 2014 9:20 AM, Jerome Glisse wrote:
> >
> > On Thu, Dec 25, 2014 at 10:29:44AM +0200, Haggai Eran wrote:
> > > On 22/12/2014 18:48, j.gli...@gmail.com wrote:
> > > > static inline void mmu_notifier_invalidate_range_start(
On Thu, Dec 25, 2014 at 10:29:44AM +0200, Haggai Eran wrote:
> On 22/12/2014 18:48, j.gli...@gmail.com wrote:
> > static inline void mmu_notifier_invalidate_range_start(struct mm_struct
> > *mm,
> > - unsigned long start,
> > -
On 22/12/2014 18:48, j.gli...@gmail.com wrote:
> static inline void mmu_notifier_invalidate_range_start(struct mm_struct *mm,
> -unsigned long start,
> -unsigned long end,
> -
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
4 matches
Mail list logo