From: Nigel Cunningham <ncunningham@cyclades.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp
Date: Thu, 30 Mar 2006 09:36:16 +1000 [thread overview]
Message-ID: <200603300936.22757.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060329150950.A12482@unix-os.sc.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
Hi.
On Thursday 30 March 2006 09:09, Ashok Raj wrote:
> On Wed, Mar 29, 2006 at 02:47:46PM -0800, Andrew Morton wrote:
> > Pavel Machek <pavel@ucw.cz> wrote:
> > > HOTPLUG_CPU is needed on normal PCs, too -- it is neccessary for
> > > software suspend.
> >
> > OK, this will get ugly. APICs are involved.
>
> I guess you need only on systems that support >1 cpu right? I doubt you
> will need it on a system that cannot run with the config-generic-arch on.
> although we use bigsmp when hotplug is turned on, all we really end up is
> using flat physical mode instead of using logical mode.
>
> I still havent understood why this wont work. Choosing
> CONFIG_X86_GENERICARCH shouldnt break anything AFAICT.
>
> Pavel, you could use CONFIG_HOTPLUG_CPU, just need to enable
> X86_GENERICARCH now. Is there a reason you think that wont work? I wish we
> would revert it for a strong reason that we know will not make hotplug work
> on certain systems because of this choise not that we currently have X86_PC
> now, and are unwiling to change the config.
>
> (PS: the word bigsmp although sounds like some large NR_CPUS, its just
> using a mode that permits the system to work from 1 .. >8 cpus. So there is
> really nothing determental to selecting this.)
So if you have a single core x86, you want X86_PC, and if you have HT or SMP,
you want GENERICARCH? If so, could this be done via selects or depends or at
least defaults in Kconfig?
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-29 23:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 22:08 [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Pavel Machek
2006-03-29 22:47 ` Andrew Morton
2006-03-29 23:09 ` Ashok Raj
2006-03-29 23:36 ` Nigel Cunningham [this message]
2006-03-29 23:47 ` Ashok Raj
2006-03-29 23:53 ` Nigel Cunningham
2006-03-30 0:12 ` Ashok Raj
2006-03-30 0:32 ` Nigel Cunningham
2006-03-30 0:13 ` Andrew Morton
2006-03-30 0:18 ` Nigel Cunningham
2006-03-30 3:01 ` Nigel Cunningham
[not found] ` <20060330030657.GA10405@mars.ravnborg.org>
2006-03-30 10:11 ` Roman Zippel
2006-03-30 8:24 ` Jan Engelhardt
2006-04-04 5:15 ` menuconfig search (Re: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp) Randy.Dunlap
2006-04-04 6:01 ` Alexey Dobriyan
2006-04-04 15:12 ` Randy.Dunlap
2006-04-08 8:42 ` Jan Engelhardt
2006-04-09 2:29 ` Randy.Dunlap
2006-04-11 11:18 ` Jan Engelhardt
2006-03-30 8:41 ` [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Pavel Machek
2006-03-30 16:17 ` Rafael J. Wysocki
2006-03-29 0:30 ` Pavel Machek
2006-04-01 23:55 ` Ashok Raj
2006-03-30 3:24 ` Andrew Morton
2006-03-30 13:00 ` Ashok Raj
2006-03-30 13:17 ` Pavel Machek
2006-03-30 13:05 ` Eric W. Biederman
2006-03-30 8:30 ` 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=200603300936.22757.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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