From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric B Munson <ebmunson@us.ibm.com>,
Eric B Munson <emunson@mgebm.net>,
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
Date: Thu, 08 Jul 2010 19:48:08 +0200 [thread overview]
Message-ID: <1278611288.1900.164.camel@laptop> (raw)
In-Reply-To: <20100708173515.GA11652@infradead.org>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric B Munson <ebmunson@us.ibm.com>,
Eric B Munson <emunson@mgebm.net>,
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
Date: Thu, 08 Jul 2010 19:48:08 +0200 [thread overview]
Message-ID: <1278611288.1900.164.camel@laptop> (raw)
In-Reply-To: <20100708173515.GA11652@infradead.org>
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, 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-07-08 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:05 [PATCH] Add trace event for munmap Eric B Munson
2010-07-08 14:05 ` Eric B Munson
2010-07-08 14:15 ` Rik van Riel
2010-07-08 14:15 ` Rik van Riel
2010-07-08 14:22 ` Peter Zijlstra
2010-07-08 14:22 ` Peter Zijlstra
2010-07-08 14:44 ` Eric B Munson
2010-07-08 17:35 ` Christoph Hellwig
2010-07-08 17:35 ` Christoph Hellwig
2010-07-08 17:48 ` Peter Zijlstra [this message]
2010-07-08 17:48 ` Peter Zijlstra
2010-07-08 17:51 ` Christoph Hellwig
2010-07-08 17:51 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1278611288.1900.164.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=ebmunson@us.ibm.com \
--cc=emunson@mgebm.net \
--cc=hch@infradead.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.