Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757174AbYBDTJT (ORCPT ); Mon, 4 Feb 2008 14:09:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755264AbYBDTJE (ORCPT ); Mon, 4 Feb 2008 14:09:04 -0500 Received: from relay1.sgi.com ([192.48.171.29]:56011 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754499AbYBDTJD (ORCPT ); Mon, 4 Feb 2008 14:09:03 -0500 Date: Mon, 4 Feb 2008 11:09:01 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andrea Arcangeli cc: Robin Holt , Avi Kivity , Izik Eidus , kvm-devel@lists.sourceforge.net, Peter Zijlstra , steiner@sgi.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com Subject: Re: [PATCH] mmu notifiers #v5 In-Reply-To: <20080203021704.GC7185@v2.random> Message-ID: References: <20080131045750.855008281@sgi.com> <20080131171806.GN7185@v2.random> <20080131234101.GS7185@v2.random> <20080201120955.GX7185@v2.random> <20080203021704.GC7185@v2.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 871 Lines: 19 On Sun, 3 Feb 2008, Andrea Arcangeli wrote: > > Right but that pin requires taking a refcount which we cannot do. > > GRU can use my patch without the pin. XPMEM obviously can't use my > patch as my invalidate_page[s] are under the PT lock (a feature to fit > GRU/KVM in the simplest way), this is why an incremental patch adding > invalidate_range_start/end would be required to support XPMEM too. Doesnt the kernel in some situations release the page before releasing the pte lock? Then there will be an external pte pointing to a page that may now have a different use. Its really bad if that pte does allow writes. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/