From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 29 Apr 2008 21:29:13 +0200 From: Ingo Molnar Subject: Re: [2/2] vmallocinfo: Add caller information Message-ID: <20080429192913.GA18279@elte.hu> References: <20080318222701.788442216@sgi.com> <20080318222827.519656153@sgi.com> <20080429084854.GA14913@elte.hu> <20080428124849.4959c419@infradead.org> <20080428140026.32aaf3bf@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: Arjan van de Ven , akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Linus Torvalds , Peter Zijlstra List-ID: * Christoph Lameter wrote: > On Mon, 28 Apr 2008, Arjan van de Ven wrote: > > > > Hmmm... Why do we have CONFIG_FRAMEPOINTER then? > > > > to make the backtraces more accurate. > > Well so we display out of whack backtraces? There are also issues on > platforms that do not have a stack in the classic sense (rotating > register file on IA64 and Sparc64 f.e.). Determining a backtrace can > be very expensive. they have to solve that for kernel oopses and for lockdep somehow anyway. Other users of stacktrace are: fault injection, kmemcheck, latencytop, ftrace. All new debugging and instrumentation code uses it, and for a good reason. Ingo -- 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: email@kvack.org