[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090306171016.GA32128@elte.hu>
Date: Fri, 6 Mar 2009 18:10:16 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Larry Woodman <lwoodman@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Nick Piggin <npiggin@...e.de>
Cc: Steven Rostedt <rostedt@...dmis.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-kernel@...r.kernel.org, peterz@...radead.org,
fweisbec@...il.com, Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [Patch] mm tracepoints
* Larry Woodman <lwoodman@...hat.com> wrote:
> > Would that be useless or controversial? We know from
> > vma->mapping which inode it maps to. Knowing which file is
> > faulting in can be useful - especially when addresses are a
> > moving target such as under PIE or with dlopen(), etc.
> >
> > Ingo
>
> Attached is the updated patch that applies and builds
> correctly (sorry I missed the lockdep tracepoints that were
> added at the last minute). [...]
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?
About the motivation of these tracepoints: i suspect these
tracepoints reflect your years-long experience in dealing with
various MM regressions in the enterprise space and these
tracepoints would help understand such regressions
faster/easier?
> [...] As far as the filename:offset is concerned I am working
> on that. Its not as simple as it looks because we have to
> follow a variable list of structs that can be null terminated
> several places along the way.
It's definitely not simple! I dont think it should be in this
base patch at all - it should be an add-on.
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