Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761613AbYB0Wvi (ORCPT ); Wed, 27 Feb 2008 17:51:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758417AbYB0Wux (ORCPT ); Wed, 27 Feb 2008 17:50:53 -0500 Received: from relay2.sgi.com ([192.48.171.30]:48605 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1761466AbYB0Wuw (ORCPT ); Wed, 27 Feb 2008 17:50:52 -0500 Date: Wed, 27 Feb 2008 14:50:50 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Jack Steiner cc: Andrea Arcangeli , Nick Piggin , akpm@linux-foundation.org, Robin Holt , Avi Kivity , Izik Eidus , kvm-devel@lists.sourceforge.net, Peter Zijlstra , general@lists.openfabrics.org, Steve Wise , Roland Dreier , Kanoj Sarcar , linux-kernel@vger.kernel.org, linux-mm@kvack.org, daniel.blueman@quadrics.com Subject: Re: [patch] my mmu notifiers In-Reply-To: <20080219142725.GA23200@sgi.com> Message-ID: References: <20080219084357.GA22249@wotan.suse.de> <20080219135851.GI7128@v2.random> <20080219142725.GA23200@sgi.com> 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: 479 Lines: 13 On Tue, 19 Feb 2008, Jack Steiner wrote: > In general, though, I agree. Most users of mmu_notifiers would likely > required a mutex or something equivalent. The skeletons shows how to do most of it using a spinlock and a counter. -- 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/