From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lameter Subject: [ofa-general] Re: [PATCH 2 of 8] Moves all mmu notifier methods outside the PT lock (first and not last Date: Wed, 2 Apr 2008 15:03:12 -0700 (PDT) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: general-bounces@lists.openfabrics.org Errors-To: general-bounces@lists.openfabrics.org To: Andrea Arcangeli Cc: Nick Piggin , Peter Zijlstra , linux-mm@kvack.org, Izik Eidus , Kanoj Sarcar , Roland Dreier , Jack Steiner , linux-kernel@vger.kernel.org, Avi Kivity , kvm-devel@lists.sourceforge.net, Robin Holt , general@lists.openfabrics.org, akpm@linux-foundation.org List-Id: linux-mm.kvack.org On Wed, 2 Apr 2008, Andrea Arcangeli wrote: > diff --git a/mm/memory.c b/mm/memory.c > --- a/mm/memory.c > +++ b/mm/memory.c > @@ -1626,9 +1626,10 @@ > */ > page_table = pte_offset_map_lock(mm, pmd, address, > &ptl); > - page_cache_release(old_page); > + new_page = NULL; > if (!pte_same(*page_table, orig_pte)) > goto unlock; > + page_cache_release(old_page); > > page_mkwrite = 1; > } This is deferring frees and not moving the callouts. KVM specific? What exactly is this doing? A significant portion of this seems to be undoing what the first patch did.