From: Andrew Morton <akpm@linux-foundation.org>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] powernow-k8: Fix section mismatch
Date: Fri, 28 May 2010 14:09:08 -0700 [thread overview]
Message-ID: <20100528140908.057f2348.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100525152858.GA24836@aftab>
On Tue, 25 May 2010 17:28:58 +0200
Borislav Petkov <borislav.petkov@amd.com> wrote:
> Fix the following warning:
>
> "WARNING: arch/x86/kernel/built-in.o(.exit.text+0x72):
> Section mismatch in reference from the function powernowk8_exit() to the variable .cpuinit.data:cpb_nb
>
> The function __exit powernowk8_exit() references a variable
> __cpuinitdata cpb_nb. This is often seen when error handling in the exit
> function uses functionality in the init path. The fix is often to remove
> the __cpuinitdata annotation of cpb_nb so it may be used outside an init
> section."
>
> Cc: <stable@kernel.org>
> Reported-by: H. Peter Anvin <hpa@zytor.com>
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
> ---
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> index 6f3dc8f..7ec2123 100644
> --- a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> +++ b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> @@ -1497,8 +1497,8 @@ static struct cpufreq_driver cpufreq_amd64_driver = {
> * simply keep the boost-disable flag in sync with the current global
> * state.
> */
> -static int __cpuinit cpb_notify(struct notifier_block *nb, unsigned long action,
> - void *hcpu)
> +static int cpb_notify(struct notifier_block *nb, unsigned long action,
> + void *hcpu)
> {
> unsigned cpu = (long)hcpu;
> u32 lo, hi;
> @@ -1528,7 +1528,7 @@ static int __cpuinit cpb_notify(struct notifier_block *nb, unsigned long action,
> return NOTIFY_OK;
> }
>
> -static struct notifier_block __cpuinitdata cpb_nb = {
> +static struct notifier_block cpb_nb = {
> .notifier_call = cpb_notify,
> };
I _think_ this is notabug. If CONFIG_HOTPLUG_CPU=y, this code/data
doesn't get discarded. If CONFIG_HOTPLUG_CPU=n,
[un]register_cpu_notifier() is a no-op.
But apparently the build system _did_ detect such a reference, so
what's going on? Maybe I'm confused again.
This code needs work. It should use hotcpu_notifier() rather than
diving down into the lower-level register_cpu_notifier(). If this is
done then linker magic will cause all the hotplug-specific code to be
omitted from vmlinux if CONFIG_HOTPLUG_CPU=n, and I suppose it will fix
the above warning.
next prev parent reply other threads:[~2010-05-28 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 15:28 [PATCH] powernow-k8: Fix section mismatch Borislav Petkov
2010-05-26 20:21 ` [tip:x86/urgent] x86, k8: Fix section mismatch for powernowk8_exit() tip-bot for Borislav Petkov
2010-05-28 21:09 ` Andrew Morton [this message]
2010-05-29 9:31 ` [PATCH] powernow-k8: Fix section mismatch Borislav Petkov
2010-05-29 9:48 ` Borislav Petkov
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=20100528140908.057f2348.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=borislav.petkov@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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