From: Eric B Munson <emunson@mgebm.net>
To: akpm@linux-foundation.org
Cc: mingo@redhat.com, hugh.dickins@tiscali.co.uk, riel@redhat.com,
peterz@infradead.org, anton@samba.org, hch@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kosaki.motohiro@jp.fujitsu.com, Eric B Munson <emunson@mgebm.net>
Subject: [PATCH 0/2 RESEND]
Date: Thu, 2 Sep 2010 14:59:43 +0100 [thread overview]
Message-ID: <1283435985-21934-1-git-send-email-emunson@mgebm.net> (raw)
This patch set is a resubmit of several patches I sent out earlier that adds
trace points to the mmap family. These events report addresses and sizes when
each function returns success. They will be used by a userspace tool that will
model memory usage.
Changes from V1:
- Group mmap, munmap, and brk into first patch (all in mmap.c) and mremap into
second (in mremap.c)
- Use DEFINE_EVENT_CLASS and DEFINE_EVENT for mmap and brk events
Eric B Munson (2):
Add trace points to mmap, munmap, and brk
Add mremap trace point
include/trace/events/mm.h | 97 +++++++++++++++++++++++++++++++++++++++++++++
mm/mmap.c | 15 ++++++-
mm/mremap.c | 4 ++
3 files changed, 115 insertions(+), 1 deletions(-)
create mode 100644 include/trace/events/mm.h
--
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 reply other threads:[~2010-09-02 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 13:59 Eric B Munson [this message]
2010-09-02 13:59 ` [PATCH 1/2] Add trace points to mmap, munmap, and brk Eric B Munson
2010-09-03 2:40 ` KOSAKI Motohiro
2010-09-02 13:59 ` [PATCH 2/2] Add mremap trace point Eric B Munson
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=1283435985-21934-1-git-send-email-emunson@mgebm.net \
--to=emunson@mgebm.net \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=hch@infradead.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox