Re: [2/2] vmallocinfo: Add caller information

[Ingo Molnar]

* Christoph Lameter <clameter@xxxxxxx> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/