[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090306180154.GA20292@elte.hu>
Date: Fri, 6 Mar 2009 19:01:54 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Larry Woodman <lwoodman@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Nick Piggin <npiggin@...e.de>,
Steven Rostedt <rostedt@...dmis.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-kernel@...r.kernel.org, fweisbec@...il.com
Subject: Re: [Patch] mm tracepoints
* Peter Zijlstra <peterz@...radead.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?
Ingo
--
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