Re: [kvm-devel] [PATCH 1 of 8] Core of mmu notifiers

2008-04-02 Thread Christoph Lameter
Thinking about this adventurous locking some more: I think you are misunderstanding what a seqlock is. It is *not* a spinlock. The critical read section with the reading of a version before and after allows you access to a certain version of memory how it is or was some time ago (caching effect

Re: [kvm-devel] [PATCH 1 of 8] Core of mmu notifiers

2008-04-02 Thread Andrea Arcangeli
On Wed, Apr 02, 2008 at 03:34:01PM -0700, Christoph Lameter wrote: > Still two methods ... Yes, the invalidate_page is called with the core VM holding a reference on the page _after_ the tlb flush. The invalidate_end is called after the page has been freed already and after the tlb flush. They've

Re: [kvm-devel] [PATCH 1 of 8] Core of mmu notifiers

2008-04-02 Thread Christoph Lameter
On Wed, 2 Apr 2008, Andrea Arcangeli wrote: > + void (*invalidate_page)(struct mmu_notifier *mn, > + struct mm_struct *mm, > + unsigned long address); > + > + void (*invalidate_range_start)(struct mmu_notifier *mn, > +

[kvm-devel] [PATCH 1 of 8] Core of mmu notifiers

2008-04-02 Thread Andrea Arcangeli
# HG changeset patch # User Andrea Arcangeli <[EMAIL PROTECTED]> # Date 1207158873 -7200 # Node ID a406c0cc686d0ca94a4d890d661cdfa48cfba09f # Parent 249e077dc932a5322e04ac1d69326622ea4023b8 Core of mmu notifiers. Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]> Signed-off-by: Nick Piggin <[EMA