public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Ashok Raj <ashok.raj@intel.com>, Andi Kleen <ak@muc.de>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org,
	Rusty Russell <rusty@rustycorp.com.au>,
	Srivattsa Vaddagiri <vatsa@in.ibm.com>
Subject: Re: [patch 1/5] x86_64: Change init sections for CPU hotplug support
Date: Thu, 2 Jun 2005 16:19:38 -0700	[thread overview]
Message-ID: <20050602161938.B16913@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506021413330.3157@montezuma.fsmlabs.com>; from zwane@arm.linux.org.uk on Thu, Jun 02, 2005 at 02:14:28PM -0600

On Thu, Jun 02, 2005 at 02:14:28PM -0600, Zwane Mwaikambo wrote:
> On Thu, 2 Jun 2005, Ashok Raj wrote:
> 
> > This patch adds __cpuinit and __cpuinitdata sections that need to exist
> > past boot to support cpu hotplug.
> > 
> > Caveat: This is done *only* for EM64T CPU Hotplug support, on request from
> > Andi Kleen. Much of the generic hotplug code in kernel, and none of the 
> > other archs that support CPU hotplug today, i386, ia64, ppc64, s390 and
> > parisc dont mark sections with __cpuinit, but only mark them as __devinit, 
> > and __devinitdata.
> > 
> > If someone is motivated to change generic code, we need to make sure all
> > existing hotplug code does not break, on other arch's that dont use 
> > __cpuinit, and __cpudevinit.
> 
> I'll do i386.
> 

The generic kernel pieces also need to be converted, which is probably the 
bigger chunk of code that could have been marked __cpuinit in cases where
hotplug is not supported.

I can do the ia64 pieces...

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

  reply	other threads:[~2005-06-02 23:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 12:57 [patch 0/5] x86_64 CPU hotplug patch series Ashok Raj
2005-06-02 12:57 ` [patch 1/5] x86_64: Change init sections for CPU hotplug support Ashok Raj
2005-06-02 20:14   ` Zwane Mwaikambo
2005-06-02 23:19     ` Ashok Raj [this message]
2005-06-02 12:57 ` [patch 2/5] x86_64: " Ashok Raj
2005-06-02 20:19   ` Zwane Mwaikambo
2005-06-02 23:33     ` Ashok Raj
2005-06-02 23:45       ` Zwane Mwaikambo
2005-06-03  0:08         ` Ashok Raj
2005-06-03  2:01       ` Shaohua Li
2005-06-03 14:25         ` Ashok Raj
2005-06-02 12:57 ` [patch 3/5] x86_64: CPU hotplug sibling map cleanup Ashok Raj
2005-06-02 12:57 ` [patch 4/5] x86_64: Dont use broadcast shortcut to make it cpu hotplug safe Ashok Raj
2005-06-02 12:58 ` [patch 5/5] x86_64: Provide ability to choose using shortcuts for IPI in flat mode Ashok Raj
2005-06-02 20:10   ` Zwane Mwaikambo
2005-06-02 23:15     ` Ashok Raj
2005-06-02 20:25 ` [patch 0/5] x86_64 CPU hotplug patch series Zwane Mwaikambo
2005-06-03 16:35   ` Andi Kleen
2005-06-03 17:15     ` Ashok Raj

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=20050602161938.B16913@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustycorp.com.au \
    --cc=vatsa@in.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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