From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 28 Apr 2008 12:48:49 -0700 From: Arjan van de Ven Subject: Re: [2/2] vmallocinfo: Add caller information Message-ID: <20080428124849.4959c419@infradead.org> In-Reply-To: References: <20080318222701.788442216@sgi.com> <20080318222827.519656153@sgi.com> <20080429084854.GA14913@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: Ingo Molnar , akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Linus Torvalds , Peter Zijlstra List-ID: On Tue, 29 Apr 2008 10:08:29 -0700 (PDT) Christoph Lameter wrote: > On Tue, 29 Apr 2008, Ingo Molnar wrote: > > > i pointed out how it should be done _much cleaner_ (and much > > smaller - only a single patch needed) via stack-trace, without > > changing a dozen architectures, and even gave a patch to make it > > all easier for you: > > > > http://lkml.org/lkml/2008/3/19/568 > > http://lkml.org/lkml/2008/3/21/88 > > > > in fact, a stacktrace printout is much more informative as well to > > users, than a punny __builtin_return_address(0)! > > Sorry lost track of this issue. Adding stracktrace support is not a > trivial thing and will change the basic handling of vmallocinfo. > > Not sure if stacktrace support can be enabled without a penalty on > various platforms. Doesnt this require stackframes to be formatted in > a certain way? it doesn't. -- 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