From: Sam Ravnborg <sam@ravnborg.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Rakib Mullick <rakib.mullick@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
markus.t.metzger@gmail.com
Subject: Re: [PATCH -mm] tracing: Fix section mismatch in trace_hw_branches.c
Date: Sun, 22 Feb 2009 20:29:09 +0100 [thread overview]
Message-ID: <20090222192909.GA28401@uranus.ravnborg.org> (raw)
In-Reply-To: <20090223010906.BD48.A69D9226@jp.fujitsu.com>
On Mon, Feb 23, 2009 at 01:15:08AM +0900, KOSAKI Motohiro wrote:
> > When I saw this patch, I searched the real purpose of __cpuinit and its
> > real impact.
> > But I didn't find any comments about it inside the kernel.
>
> AFAIK, __cpuinit mean
>
> if UP, __cpuinit == __init
> if SMP=Y && HOTPLUG_CPU=y, __cpuinit == "" (do nothing)
> if SMP=Y && HOTPLUG_CPU=n, __cpuinit == __init
A function annotated __cpuinit always end up in the same section these
days. And that section are then:
if HOTPLUG_CPU=y, __cpuinit => kept
if HOTPLUG_CPU=n, __cpuinit => discarded
SMP has no influence.
Sam
prev parent reply other threads:[~2009-02-22 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 3:36 [PATCH -mm] tracing: Fix section mismatch in trace_hw_branches.c Rakib Mullick
2009-02-15 19:41 ` Ingo Molnar
2009-02-21 15:22 ` Frederic Weisbecker
2009-02-22 13:33 ` Rakib Mullick
2009-02-22 16:22 ` Frederic Weisbecker
2009-02-23 10:21 ` Markus Metzger
2009-02-22 16:15 ` KOSAKI Motohiro
2009-02-22 16:23 ` Frederic Weisbecker
2009-02-22 19:29 ` Sam Ravnborg [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=20090222192909.GA28401@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.