On Wed, 2010-03-24 at 18:35 +0100, John Kacur wrote: > This reverts commit 3e39399ef4a742d994570488994be93ef17d4ef5. > > CONFIG_STACK_TRACER really should not be in the reminder block. > By default it is not enabled, and has negligible impact. Correct, the stack trace is based off of the function tracer, which with dynamic ftrace it does not have any extra impact when not enabled. Hmm, maybe we should add a warning if it was set on the command line? Anyway, Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx> -- Steve > > Signed-off-by: John Kacur <jkacur@xxxxxxxxxx> > --- > init/main.c | 3 --- > 1 files changed, 0 insertions(+), 3 deletions(-) > > diff --git a/init/main.c b/init/main.c > index 48393c0..aa48b7b 100644 > --- a/init/main.c > +++ b/init/main.c > @@ -928,9 +928,6 @@ static int __init kernel_init(void * unused) > #ifdef CONFIG_PREEMPT_TRACER > printk(KERN_ERR "* CONFIG_PREEMPT_TRACER *\n"); > #endif > -#ifdef CONFIG_STACK_TRACER > - printk(KERN_ERR "* CONFIG_STACK_TRACER *\n"); > -#endif > #if defined(CONFIG_FTRACE) && !defined(CONFIG_FTRACE_MCOUNT_RECORD) > printk(KERN_ERR "* CONFIG_FTRACE *\n"); > #endif -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
