public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Paul Mundt <lethal@linux-sh.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: mm: memory/cpu hotplug section mismatch.
Date: Mon, 11 Jun 2007 20:40:46 +0200	[thread overview]
Message-ID: <20070611184046.GA6458@uranus.ravnborg.org> (raw)
In-Reply-To: <20070611154428.GA27644@linux-sh.org>

> 
> If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
> CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
> other disabled, you end up with a reference between __init and a regular
> non-init function.

My plan is to define dedicated sections for both __devinit and __meminit.
Then we can apply the checks no matter the definition of CONFIG_HOTPLUG*
But we are a few steps away form doing so:
1) All harcoded uses of .init.text needs to go (at least done in assembler files)
2) The arch lds files needs to be unified a bit too.

Then we can during the final link stage decide if __devinit shall be merged
into .text or .init.text (after applying the modpost checks).

But do not hold your breath.

The even more important precondition is to sort out all the current
section mismatch warnings. But here we are getting close.

	Sam

  reply	other threads:[~2007-06-11 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11  4:35 mm: memory/cpu hotplug section mismatch Paul Mundt
2007-06-11  5:01 ` KAMEZAWA Hiroyuki
2007-06-11  5:09   ` Paul Mundt
2007-06-11 15:27     ` Randy Dunlap
2007-06-11 15:44       ` Paul Mundt
2007-06-11 18:40         ` Sam Ravnborg [this message]
2007-06-12  1:50           ` Yasunori Goto
2007-06-12  3:19             ` Paul Mundt

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=20070611184046.GA6458@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=randy.dunlap@oracle.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