Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758125Ab0GHRv5 (ORCPT ); Thu, 8 Jul 2010 13:51:57 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:50963 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754752Ab0GHRv4 (ORCPT ); Thu, 8 Jul 2010 13:51:56 -0400 Date: Thu, 8 Jul 2010 13:51:48 -0400 From: Christoph Hellwig To: Peter Zijlstra Cc: Christoph Hellwig , Eric B Munson , Eric B Munson , akpm@linux-foundation.org, mingo@redhat.com, hugh.dickins@tiscali.co.uk, riel@redhat.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, anton@samba.org Subject: Re: [PATCH] Add trace event for munmap Message-ID: <20100708175147.GA17525@infradead.org> References: <1278597931-26855-1-git-send-email-emunson@mgebm.net> <1278598955.1900.152.camel@laptop> <20100708144407.GA8141@us.ibm.com> <20100708173515.GA11652@infradead.org> <1278611288.1900.164.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1278611288.1900.164.camel@laptop> User-Agent: Mutt/1.5.20 (2009-08-17) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 26 On Thu, Jul 08, 2010 at 07:48:08PM +0200, Peter Zijlstra wrote: > On Thu, 2010-07-08 at 13:35 -0400, Christoph Hellwig wrote: > > > What kind of infrastructure is perf using for recording > > mmap()/mremap()/brk() information? > > A direct hook into mmap_region(), see perf_event_mmap(). > > We used to only track VM_EXEC regions, but these days we can also track > data regions (although it wouldn't track mremap and brk I think). > > We need the VM_EXEC maps to make sense of the instruction pointer > samples. > > Eric recently added support for !VM_EXEC mmap() in order to interpret > linear addresses provided by things like the software pagefault events > and certain powerpc hardware events. Maybe the user reporting should use trace points everywhere, leaving the direct hook just for the executable tracking? -- 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/