From: Milton Miller <miltonm@bga.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-ppc <linuxppc-dev@ozlabs.org>, Nathan Lynch <ntl@pobox.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Remove modpost warning with start_secondary (Modified by Milton Miller)
Date: Thu, 4 Dec 2008 11:16:22 -0600 [thread overview]
Message-ID: <0ff42e9c3d9aabbda3102f25bc7bfa2c@bga.com> (raw)
In-Reply-To: <20081203174340.GA6958@localdomain>
[oops forgot to cc the list]
Nathan Lynch wrote at 2008-12-03 17:43:40:
> Kumar Gala wrote:
>> On Dec 2, 2008, at 11:31 PM, Nathan Lynch wrote:
>>> Kumar Gala wrote:
>>>> WARNING: vmlinux.o(.text+0x2aa): Section mismatch in reference from
>>>> the variable __secondary_start to the function
>>>> .devinit.text:start_secondary()
>>>> The function __secondary_start() references
>>>> the function __devinit start_secondary().
>>>>
>>>> start_secondary gets called by __secondary_start which is in asm
>>>> code so its
>>>> not marked as __devinit. Its easier to just remove the __devinit
>>>> from
>>>> start_secondary than try and deal with __secondary_start.
>>>
>>> Which just gets another mismatch warning here:
>>>
>>> WARNING: arch/powerpc/kernel/built-in.o(.text+0x23cc4): Section
>>> mismatch in reference from the function .start_secondary() to the
>>> function .devinit.text:.smp_store_cpu_info()
>>> The function .start_secondary() references
>>> the function __devinit .smp_store_cpu_info().
>>> This is often because .start_secondary lacks a __devinit
>>> annotation or the annotation of .smp_store_cpu_info is wrong.
And other architectures want this to be cpuinit, the patch is held up
because of powerpc:
http://ozlabs.org/pipermail/linuxppc-dev/2008-November/064897.html
>>> Isn't there a better way to address this? It doesn't seem right to
>>> increase the kernel's memory usage to get rid of a modpost warning.
I agree. And its easy: move the asm code to the right section with the
nifty macros in linux/init.h.
We can use the whitelist of .text.head and also use use cpuinit.
I had a patch last July that went in this direction, but it was tangled
with the relocatable kernel patches and badly timed.
http://ozlabs.org/pipermail/linuxppc-dev/2008-July/059717.html
hmm, I don't see 1/3 that cleaned up the function entry macro repition.
I'll try to revive them and bring them up to the current tree.
>>
>> Fair.. what defconfig did you build?
>
> Try ppc64_defconfig with HOTPLUG_CPU=n.
milton
prev parent reply other threads:[~2008-12-04 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 4:32 [PATCH] powerpc: Remove modpost warning with start_secondary Kumar Gala
2008-12-03 5:31 ` Nathan Lynch
2008-12-03 14:48 ` Kumar Gala
2008-12-03 17:43 ` Nathan Lynch
2008-12-04 17:16 ` Milton Miller [this message]
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=0ff42e9c3d9aabbda3102f25bc7bfa2c@bga.com \
--to=miltonm@bga.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).