public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Jones <davej@redhat.com>,
	Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
	Andrew Morton <akpm@osdl.org>, Ashok Raj <ashok.raj@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: [patch -mm4] i386: __init should be __cpuinit
Date: Wed, 1 Feb 2006 11:15:54 -0800	[thread overview]
Message-ID: <20060201111554.A21287@unix-os.sc.intel.com> (raw)
In-Reply-To: <1138820183.3943.11.camel@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 01, 2006 at 06:56:22PM +0000

On Wed, Feb 01, 2006 at 06:56:22PM +0000, Alan Cox wrote:
> On Mer, 2006-02-01 at 11:03 -0500, Dave Jones wrote:
> >  > For SMP systems, suspend/resume "unplugs" all non-boot CPUs before
> >  > executing the suspend code. I don't recall any SMP cyrix systems, but
> >  > it's potentially something to consider.
> > 
> > There weren't any.  Until AMD's Athlon MPs, Intel had the only
> > SMP x86 afair.
> 
> Several vendors demonstrated OpenMP designs including Cyrix. Nothing
> production and nothing we support.

In order to support logical cpu hotplug, you dont need any special hw, as long
as you has some SMP box. Sometimes its just a little bit more than 
moving __init to __cpuinit. A lot of these references were not changed
just speculatively to ensure when the need is there, someone will change and
test those as well.

Chuck, would it be possible for you also test cpu hotplug for the ones you 
are interested in and accompany the related changes if there are more
as separate patches? (Documentation now has a howto on cpu hotplug)

That would make it more useful for this exersise.

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

  reply	other threads:[~2006-02-01 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  4:49 [patch -mm4] i386: __init should be __cpuinit Chuck Ebbert
2006-02-01  5:33 ` Dave Jones
2006-02-01  8:05   ` Matthew Garrett
2006-02-01 16:03     ` Dave Jones
2006-02-01 18:56       ` Alan Cox
2006-02-01 19:15         ` Ashok Raj [this message]
2006-02-02 21:34   ` Pavel Machek
2006-02-02 21:39     ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01  8:03 Chuck Ebbert

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=20060201111554.A21287@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarrett@chiark.greenend.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