Messages in this thread Patch in this message | | | Date | Fri, 21 Mar 2008 12:00:08 +0100 | From | Ingo Molnar <> | Subject | Re: [2/2] vmallocinfo: Add caller information |
| |
* Christoph Lameter <clameter@sgi.com> wrote:
> On Wed, 19 Mar 2008, Ingo Molnar wrote: > > > > > * Christoph Lameter <clameter@sgi.com> wrote: > > > > > Add caller information so that /proc/vmallocinfo shows where the > > > allocation request for a slice of vmalloc memory originated. > > > > please use one simple save_stack_trace() instead of polluting a dozen > > architectures with: > > save_stack_trace() depends on CONFIG_STACKTRACE which is only > available when debugging is compiled it. I was more thinking about > this as a generally available feature.
then make STACKTRACE available generally via the patch below.
Ingo
-------------------------------------------> Subject: debugging: always enable stacktrace From: Ingo Molnar <mingo@elte.hu> Date: Fri Mar 21 11:48:32 CET 2008
Signed-off-by: Ingo Molnar <mingo@elte.hu> --- lib/Kconfig.debug | 1 - 1 file changed, 1 deletion(-)
Index: linux-x86.q/lib/Kconfig.debug =================================================================== --- linux-x86.q.orig/lib/Kconfig.debug +++ linux-x86.q/lib/Kconfig.debug @@ -387,7 +387,6 @@ config DEBUG_LOCKING_API_SELFTESTS config STACKTRACE bool - depends on DEBUG_KERNEL depends on STACKTRACE_SUPPORT config DEBUG_KOBJECT
| |