From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: kosaki.motohiro@jp.fujitsu.com, Eric B Munson <emunson@mgebm.net>,
akpm@linux-foundation.org, mingo@redhat.com,
hugh.dickins@tiscali.co.uk, riel@redhat.com,
peterz@infradead.org, anton@samba.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] Add trace events to mmap and brk
Date: Mon, 12 Jul 2010 10:58:01 +0900 (JST) [thread overview]
Message-ID: <20100712104602.EA1A.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20100709160342.GB3281@infradead.org>
> Hmm, thinking about it a bit more, what do you trace events give us that
> the event based syscall tracer doesn't?
Yup. I think we need two tracepoint.
1) need to know userland argument.
-> syscall tracer
2) need to know actual vma change.
-> need to trace more low layer
As I said, if userland app have following code,
mmap(0x10000, PROT_READ|PROT_WRITE)
mmap(0x10000, PROT_NONE)
second mmap implicitly unmap firt mmap region and map another region.
so if we want to track munmap activity, syscall exiting point is not
so good place. we need to trace per-vma activity.
btw, perf_event_mmap() already take vma argument.
--
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-12 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 15:53 Eric B Munson
2010-07-09 15:53 ` [PATCH 2/2] Add trace point to mremap Eric B Munson
2010-07-09 16:02 ` Christoph Hellwig
2010-07-09 16:03 ` [PATCH 1/2] Add trace events to mmap and brk Christoph Hellwig
2010-07-12 1:58 ` KOSAKI Motohiro [this message]
2010-07-10 1:17 ` Steven Rostedt
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=20100712104602.EA1A.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--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=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