[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111117055904.GA15644@zhy>
Date: Thu, 17 Nov 2011 13:59:04 +0800
From: Yong Zhang <yong.zhang0@...il.com>
To: tom.leiming@...il.com
Cc: mingo@...e.hu, a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] init/main.c: execute lockdep_init as early as
possible
On Thu, Nov 17, 2011 at 01:34:31PM +0800, tom.leiming@...il.com wrote:
> From: Ming Lei <tom.leiming@...il.com>
>
> This patch removes the lockdep warning[1] on ARM platform.
> The warning is caused by printk inside smp_setup_processor_id.
>
> It is safe to do this because lockdep_init doesn't depend on
> smp_setup_processor_id, so make printk can be called as early
> as possible without lockdep complainment.
>
> [1], lockdep warning
> [ 0.000000] WARNING: lockdep init error! Arch code didn't call
> lockdep_init() early enough?
> [ 0.000000] Call stack leading to lockdep invocation was:
> [ 0.000000] [<c00164bc>] save_stack_trace_tsk+0x0/0x90
> [ 0.000000] [<ffffffff>] 0xffffffff
>
> Signed-off-by: Ming Lei <tom.leiming@...il.com>
Seems start_kernel() is the first C function called in arm.
IOW, this may be the simplest way for your issue.
Reviewed-by: Yong Zhang <yong.zhang0@...il.com>
> ---
> init/main.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/init/main.c b/init/main.c
> index 217ed23..2c76efb 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -469,13 +469,12 @@ asmlinkage void __init start_kernel(void)
> char * command_line;
> extern const struct kernel_param __start___param[], __stop___param[];
>
> - smp_setup_processor_id();
> -
> /*
> * Need to run as early as possible, to initialize the
> * lockdep hash:
> */
> lockdep_init();
> + smp_setup_processor_id();
> debug_objects_early_init();
>
> /*
> --
> 1.7.5.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Only stand for myself
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists