All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nathan Lynch <ntl@pobox.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	rusty@rustcorp.com.au
Subject: Re: CPU hotplug on i386
Date: Thu, 17 Mar 2005 01:04:10 +0100	[thread overview]
Message-ID: <20050317000410.GA3210@elf.ucw.cz> (raw)
In-Reply-To: <200503170051.58579.rjw@sisk.pl>

Hi!

> > > I tried to solve long-standing uglyness in swsusp cmp code by calling
> > > cpu hotplug... only to find out that CONFIG_CPU_HOTPLUG is not
> > > available on i386. Is there way to enable CPU_HOTPLUG on i386?
> > 
> > i386 cpu hotplug has been in -mm for a while.  Don't know when (if
> > ever) it will get merged.
> 
> Thanks a lot for this hint! ;-)
> 
> Pavel, I've ported the basic i386 CPU hotplug stuff, without the sysfs
> interface, to x86-64 (a cut'n'paste kind of work, mostly).  For now, I've
> made HOTPLUG_CPU on x86-64 depend on SMP and SOFTWARE_SUSPEND and be set
> automatically.
> 
> I'm going to test it together with your patch tomorrow.

Hey, don't count on my patch. It is first shot, never tested.

									Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-03-17  0:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 13:21 CPU hotplug on i386 Pavel Machek
2005-03-16 14:40 ` Rafael J. Wysocki
2005-03-17  0:40   ` Nigel Cunningham
2005-03-16 17:09 ` Nathan Lynch
2005-03-16 19:20   ` Zwane Mwaikambo
2005-03-16 23:51   ` Rafael J. Wysocki
2005-03-17  0:04     ` Pavel Machek [this message]
2005-03-17  0:16       ` Rafael J. Wysocki
2005-03-16 18:49 ` Nathan Lynch
2005-03-16 20:51   ` Pavel Machek
2005-03-18 11:45 ` Pavel Machek

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=20050317000410.GA3210@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntl@pobox.com \
    --cc=rjw@sisk.pl \
    --cc=rusty@rustcorp.com.au \
    /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.