lkml.org 
[lkml]   [2008]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [2/2] vmallocinfo: Add caller information

* Christoph Lameter <clameter@sgi.com> 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


\
 
 \ /
  Last update: 2008-03-21 21:59    [W:0.044 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site