linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: johlstei@codeaurora.org (Jeff Ohlstein)
To: linux-arm-kernel@lists.infradead.org
Subject: hotplug and init section
Date: Tue, 03 Aug 2010 15:31:09 -0700	[thread overview]
Message-ID: <4C5898AD.9020300@codeaurora.org> (raw)
In-Reply-To: <20100722205753.GU31293@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Thu, Jul 22, 2010 at 12:33:08PM -0700, smuckle at codeaurora.org wrote:
>> Changing things so
>> that the code required for bringing up secondary cores is still present
>> after init looks to be a fairly big change. As such I wanted to see if
>> anyone had thoughts here before I start hacking up head.S, the linker
>> script, etc.
>>     
>
> No need to hack the linker script - all you need to do is to ensure that
> the required parts of code are placed in the cpuinit sections - and there's
> a macro to do that called "__CPUINIT" (which equates to a .section
> directive.)
>
> You'll need to ensure that stuff which shouldn't be in the cpuinit
> section remains as-is, so you'll have to also add __INIT or
> .section .text as appropriate.
>   
So I've been looking into this, and it does look like I need to change 
the linker script. I need the secondary_startup function to be around at 
hotplug time, and it appears that the whole head section gets freed with 
the init section. Does it seem sane to make it so the head section isn't 
freed when hotplug is configured? Or should I move the secondary startup 
function out of the head section?

Thanks,
Jeff

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-08-03 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 19:33 hotplug and init section smuckle at codeaurora.org
2010-07-22 20:57 ` Russell King - ARM Linux
2010-08-03 22:31   ` Jeff Ohlstein [this message]
2010-08-03 23:05     ` Russell King - ARM Linux
2010-08-04  0:51       ` Jeff Ohlstein
2010-08-04 17:56         ` Russell King - ARM Linux
2010-07-23  5:20 ` Shilimkar, Santosh

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=4C5898AD.9020300@codeaurora.org \
    --to=johlstei@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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).