From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Larry Woodman <lwoodman@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Steven Rostedt <rostedt@goodmis.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, fweisbec@gmail.com
Subject: Re: [Patch] mm tracepoints
Date: Fri, 06 Mar 2009 19:20:25 +0100 [thread overview]
Message-ID: <1236363625.6326.641.camel@laptop> (raw)
In-Reply-To: <20090306180154.GA20292@elte.hu>
On Fri, 2009-03-06 at 19:01 +0100, Ingo Molnar wrote:
> * Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Fri, 2009-03-06 at 18:38 +0100, Peter Zijlstra wrote:
> > > On Fri, 2009-03-06 at 18:10 +0100, Ingo Molnar wrote:
> > > > Looks pretty good and useful to me. I've Cc:-ed more mm folks,
> > > > it would be nice to hear their opinion about these tracepoints.
> > > >
> > > > Andrew, Nick, Peter, what do you think?
> > >
> > > Bit sad we use the struct mm_struct * as mm identifier (little %lx vs %p
> > > confusion there too), but I suppose there simply isn't anything better.
> >
> > > Things missing,
> >
> > Why only anon and filemap, that misses out on all the funky
> > driver ->fault() handlers.
>
> btw., does it include shm faults? I think all of this would be
> handled if the tracepoint was at handle_mm_fault(), right?
Partially, you wouldn't be able to do the file:offset thing you asked
for.
But yeah, also hugetlb seems to be missing.
next prev parent reply other threads:[~2009-03-06 18:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 15:38 marching through all physical memory in software Chris Friesen
2009-01-26 15:59 ` Arjan van de Ven
2009-01-27 18:29 ` Chris Friesen
2009-01-27 20:16 ` Eric W. Biederman
2009-01-28 19:38 ` Pavel Machek
2009-01-30 9:05 ` Nigel Cunningham
2009-01-30 9:13 ` Pavel Machek
2009-01-30 13:00 ` Nigel Cunningham
2009-03-05 22:16 ` [Patch] mm tracepoints Larry Woodman
2009-03-06 2:11 ` KOSAKI Motohiro
2009-03-06 2:26 ` Steven Rostedt
2009-03-06 11:04 ` Ingo Molnar
2009-03-06 12:33 ` Larry Woodman
2009-03-06 13:55 ` Ingo Molnar
2009-03-06 16:57 ` Larry Woodman
2009-03-06 17:10 ` Ingo Molnar
2009-03-06 17:38 ` Peter Zijlstra
2009-03-06 17:46 ` Ingo Molnar
2009-03-06 17:56 ` Peter Zijlstra
2009-03-06 18:01 ` Ingo Molnar
2009-03-06 18:20 ` Peter Zijlstra [this message]
2009-03-06 18:24 ` Ingo Molnar
2009-03-06 20:01 ` Larry Woodman
2009-03-06 19:06 ` Larry Woodman
2009-03-06 21:53 ` Chris Friesen
2009-03-06 19:22 ` Larry Woodman
2009-03-25 18:09 ` Latest mm tracepoints patch merged to your tip tree Larry Woodman
2009-03-06 21:16 ` [Patch] mm tracepoints Andrew Morton
2009-02-06 9:00 ` marching through all physical memory in software Andi Kleen
2009-02-07 3:03 ` Henrique de Moraes Holschuh
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=1236363625.6326.641.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=rostedt@goodmis.org \
/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