From: Ingo Molnar <mingo@elte.hu>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kernel/cpu.c: Section mismatch warning fix.
Date: Thu, 30 Oct 2008 19:26:01 +0100 [thread overview]
Message-ID: <20081030182601.GE14102@elte.hu> (raw)
In-Reply-To: <b9df5fa10810292104h38fcee68kae42cf5ab6275fbb@mail.gmail.com>
* Rakib Mullick <rakib.mullick@gmail.com> wrote:
> LD kernel/built-in.o
> WARNING: kernel/built-in.o(.text+0xb7c8): Section mismatch in
> reference from the function notify_cpu_starting() to the variable
> .cpuinit.data:cpu_chain
> The function notify_cpu_starting() references
> the variable __cpuinitdata cpu_chain.
> This is often because notify_cpu_starting lacks a __cpuinitdata
> annotation or the annotation of cpu_chain is wrong.
>
> This patch fixes the above section mismatch warning. If anything else
> please notice.
> Thanks.
>
> Signed-off-by: Md.Rakib H. Mullick <rakib.mullick@gmail.com>
>
> --- linux-2.6-orig/kernel/cpu.c 2008-10-28 20:52:38.000000000 +0600
> +++ linux-2.6/kernel/cpu.c 2008-10-28 22:46:22.000000000 +0600
> @@ -462,7 +462,7 @@ out:
> * It must be called by the arch code on the new cpu, before the new cpu
> * enables interrupts and before the "boot" cpu returns from __cpu_up().
> */
> -void notify_cpu_starting(unsigned int cpu)
> +void __cpuinit notify_cpu_starting(unsigned int cpu)
> {
> unsigned long val = CPU_STARTING;
you've tested that on x86, right? Have you checked/reviewed all the
non-x86 architecture codepaths:
./arch/m32r/kernel/smpboot.c: notify_cpu_starting(cpu_id);
./arch/cris/arch-v32/kernel/smp.c: notify_cpu_starting(cpu);
./arch/s390/kernel/smp.c: notify_cpu_starting(smp_processor_id());
./arch/x86/mach-voyager/voyager_smp.c: notify_cpu_starting(cpuid);
./arch/x86/kernel/smpboot.c: notify_cpu_starting(cpuid);
./arch/mips/kernel/smp.c: notify_cpu_starting(cpu);
./arch/sparc64/kernel/smp.c: notify_cpu_starting(cpuid);
./arch/ia64/kernel/smpboot.c: notify_cpu_starting(cpuid);
./arch/um/kernel/smp.c: notify_cpu_starting(cpu);
./arch/sparc/kernel/sun4d_smp.c: notify_cpu_starting(cpuid);
./arch/sparc/kernel/sun4m_smp.c: notify_cpu_starting(cpuid);
./arch/powerpc/kernel/smp.c: notify_cpu_starting(cpu);
./arch/alpha/kernel/smp.c: notify_cpu_starting(cpuid);
./arch/sh/kernel/smp.c: notify_cpu_starting(smp_processor_id());
./arch/arm/kernel/smp.c: notify_cpu_starting(cpu);
to make sure that they never use this function after free_initmem()?
Ingo
next prev parent reply other threads:[~2008-10-30 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 4:04 Rakib Mullick
2008-10-30 18:26 ` Ingo Molnar [this message]
2008-11-02 1:59 ` Rakib Mullick
2008-11-03 10:15 ` Ingo Molnar
2008-11-03 23:34 ` Andrew Morton
2008-11-04 9:48 ` Ingo Molnar
2008-11-04 10:09 ` Sam Ravnborg
2008-11-04 10:22 ` Ingo Molnar
2008-11-04 11:02 ` Sam Ravnborg
2008-11-04 13:06 ` James Bottomley
2008-11-04 13:22 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081030182601.GE14102@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rakib.mullick@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®