[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1278611288.1900.164.camel@laptop>
Date: Thu, 08 Jul 2010 19:48:08 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Eric B Munson <ebmunson@...ibm.com>,
Eric B Munson <emunson@...bm.net>, akpm@...ux-foundation.org,
mingo@...hat.com, hugh.dickins@...cali.co.uk, riel@...hat.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, anton@...ba.org
Subject: Re: [PATCH] Add trace event for munmap
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists