From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 21 Mar 2008 21:55:59 +0100 From: Ingo Molnar Subject: Re: [2/2] vmallocinfo: Add caller information Message-ID: <20080321205559.GC3509@elte.hu> References: <20080318222701.788442216@sgi.com> <20080318222827.519656153@sgi.com> <20080319214227.GA4454@elte.hu> <20080321110008.GW20420@elte.hu> <20080321184526.GB6571@elte.hu> 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: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: * Christoph Lameter wrote: > > the best i found for lockdep was to include a fair number of them, > > and to skip the top 3. struct vm_area that vmalloc uses isnt > > space-critical, so 4-8 entries with a 3 skip would be quite ok. (but > > can be more than that as well) > > STACKTRACE depends on STACKTRACE_SUPPORT which is not available on all > arches? alpha blackfin ia64 etc are missing it? one more reason for them to implement it. > I thought there were also issues on x86 with optimizations leading to > weird stacktraces? at most there can be extra stack trace entries. This is for debugging, so if someone wants exact stacktraces, FRAME_POINTERS will certainly improve them. 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