On Fri, 21 Mar 2008, Ingo Molnar wrote:
quoted text > 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?
I thought there were also issues on x86 with optimizations leading to
weird stacktraces?
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [2/2] vmallocinfo: Add caller information , Christoph Lameter , (Fri Mar 21, 12:16 pm)