Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760380AbYAYV0A (ORCPT ); Fri, 25 Jan 2008 16:26:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754388AbYAYVZw (ORCPT ); Fri, 25 Jan 2008 16:25:52 -0500 Received: from relay2.sgi.com ([192.48.171.30]:46089 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755404AbYAYVZv (ORCPT ); Fri, 25 Jan 2008 16:25:51 -0500 Date: Fri, 25 Jan 2008 13:25:50 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Benjamin Herrenschmidt cc: Andrea Arcangeli , Robin Holt , Avi Kivity , Izik Eidus , Nick Piggin , kvm-devel@lists.sourceforge.net, Peter Zijlstra , steiner@sgi.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com, Hugh Dickins Subject: Re: [patch 0/4] [RFC] MMU Notifiers V1 In-Reply-To: <1201295921.6815.150.camel@pasglop> Message-ID: References: <20080125055606.102986685@sgi.com> <20080125114229.GA7454@v2.random> <1201295921.6815.150.camel@pasglop> 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: 788 Lines: 16 On Sat, 26 Jan 2008, Benjamin Herrenschmidt wrote: > Also, wouldn't there be a problem with something trying to use that > interface to keep in sync a secondary device MMU such as the DRM or > other accelerators, which might need virtual address based > invalidation ? Yes just doing the rmap based solution would have required DRM etc to maintain their own rmaps. So it looks that we need to go with both variants. Note that secondary device MMUs that need to run code outside of atomic context may still need to create their own rmaps. -- 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/