Re: [2/2] vmallocinfo: Add caller information
From: Ingo Molnar
Date: Fri Mar 21 2008 - 07:00:38 EST
* Christoph Lameter <clameter@xxxxxxx> wrote:
> On Wed, 19 Mar 2008, Ingo Molnar wrote:
>
> >
> > * Christoph Lameter <clameter@xxxxxxx> 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@xxxxxxx>
Date: Fri Mar 21 11:48:32 CET 2008
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
---
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
--
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/