From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 24 Jan 2008 12:07:52 -0800 (PST) From: Christoph Lameter Subject: Re: [kvm-devel] [PATCH] export notifier #1 In-Reply-To: <20080124154239.GP7141@v2.random> Message-ID: References: <4795F9D2.1050503@qumranet.com> <20080122144332.GE7331@v2.random> <20080122200858.GB15848@v2.random> <20080122223139.GD15848@v2.random> <20080123114136.GE15848@v2.random> <20080123123230.GH26420@sgi.com> <20080123173325.GG7141@v2.random> <20080124154239.GP7141@v2.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Andrea Arcangeli Cc: Robin Holt , Avi Kivity , Izik Eidus , Andrew Morton , Nick Piggin , kvm-devel@lists.sourceforge.net, Benjamin Herrenschmidt , steiner@sgi.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com, Hugh Dickins List-ID: On Thu, 24 Jan 2008, Andrea Arcangeli wrote: > I think you should consider if you can also build a rmap per-MM like > KVM does and index it by the virtual address like KVM does. Yes we have that. If we have that then we do not need the mmu_notifier. We could call it with a page parameter and then walk the KVM or XPmem reverse map to directly find all the ptes we need to clear. There is no need then to add a new field to the mm_struct. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org