public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: zwane@arm.linux.org.uk, discuss@x86-64.org, shaohua.li@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2/4] CPU hot-plug support for x86_64
Date: 23 May 2005 19:24:24 +0200
Date: Mon, 23 May 2005 19:24:24 +0200	[thread overview]
Message-ID: <20050523172424.GG39821@muc.de> (raw)
In-Reply-To: <20050523095816.B8193@unix-os.sc.intel.com>

On Mon, May 23, 2005 at 09:58:17AM -0700, Ashok Raj wrote:
> On Mon, May 23, 2005 at 06:38:16PM +0200, Andi Kleen wrote:
> > On Fri, May 20, 2005 at 03:16:24PM -0700, Ashok Raj wrote:
> > > Experimental CPU hotplug patch for x86_64
> > > -----------------------------------------
> > > - Most of init code that needs to be there for hotplug marked now as __devinit
> > > 	(Didn't use cpuinit, simply because the main framework code in kernel
> > > 	 is not the same way, just trying to be consistent)
> > 
> > I dont like that. Can you keep it as __cpuinit please?  e.g. 
> > if cpuhot plug turns out to be a lot of code we could later
> > mark it free when we detect at boot the system does not support
> > cpu hotplug. With devinit that is pretty much impossible these days.
> > 
> > Also it is better for documentation purposes.
> 
> If its for documentation, then its ok, the reason i thought it will
> be dead code/documentation soon is since 90% of the hotplug code is
> generic kernel code, which is not under __cpuinit, just some pieces of 
> x86_64 would alone exist this way, and will not serve real purpose very soon.

I would hope these other pieces get converted over. I will probably
look into that soon if nobody beats me.

-Andi

  reply	other threads:[~2005-05-23 17:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 22:16 [patch 0/4] CPU hot-plug support for x86_64 Ashok Raj
2005-05-20 22:16 ` [patch 1/4] " Ashok Raj
2005-05-20 22:16 ` [patch 2/4] " Ashok Raj
2005-05-23 16:38   ` Andi Kleen
2005-05-23 16:58     ` Ashok Raj
2005-05-23 17:24       ` Andi Kleen [this message]
2005-05-23 17:32         ` Ashok Raj
2005-05-23 19:37     ` Rafael J. Wysocki
2005-05-24 11:49       ` Andi Kleen
2005-05-20 22:16 ` [patch 3/4] " Ashok Raj
2005-05-20 22:16 ` [patch 4/4] " Ashok Raj
2005-05-23 16:40 ` [patch 0/4] " Andi Kleen
2005-05-23 16:54   ` Ashok Raj
2005-05-23 17:12     ` Andi Kleen
2005-05-23 17:40       ` [discuss] " Ashok Raj
2005-05-24  5:46         ` Srivatsa Vaddagiri
2005-05-24  6:01           ` Ashok Raj
2005-05-24  8:53             ` Srivatsa Vaddagiri
2005-05-24 18:17               ` Andi Kleen
2005-05-24 11:50           ` Andi Kleen
2005-05-24 11:48         ` Andi Kleen
2005-05-24 17:01           ` Srivatsa Vaddagiri

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=20050523172424.GG39821@muc.de \
    --to=ak@muc.de \
    --cc=ashok.raj@intel.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.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