mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm@osdl.org
Subject: Re: Linux v2.6.16
Date: Thu, 23 Mar 2006 09:27:43 +1100	[thread overview]
Message-ID: <4421CF5F.7010402@bigpond.net.au> (raw)
In-Reply-To: <20060321223120.A4003@unix-os.sc.intel.com>

Ashok Raj wrote:
> On Tue, Mar 21, 2006 at 09:22:41PM -0800, Peter Williams wrote:
> 
>>   I/O APICs
>>   Mar 22 16:10:31 heathwren kernel: More than 8 CPUs detected and
>>   CONFIG_X86_PC cannot handle it.
>>
>>   ###  No more CPUs seen but something in there thinks there's more than
>>   8
>>   of them.
>>
>>   Mar 22 16:10:31 heathwren kernel: Use CONFIG_X86_GENERICARCH or
>>   CONFIG_X86_BIGSMP.
>>
> 
> 
> 
> This was disussed here,  
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114228068804099&w=2
> 
> but we didnt yet close out on it, Andrew didnt feel comfortable
> making CONFIG_HOTPLUG_CPU depend on !X86_PC, and making it depend on CONFIG_GENERICARCH
> or CONFIG_BIGSMP this late in the process.
> 
> The warning is bogus,

That's what I thought but I thought I should still report it as bogus 
messages can cause people to become inured and ignore real ones.

> when BIGSMP was first introduced it was solely to handle >8 CPUS
> using custer mode configuration. We switched bigsmp to use flat physical mode just like 
> what we do for x86_64, because some chipsets have ill effects with cpu hotplug.
> when we wakeup a new cpu. Details here
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=113261865814107&w=2
> 
> Hence we switched to bigsmp, but the error message was not reworked, better yet is
> to have the right config depends so we dont run into any race and instability issues.
> 
> 

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

  parent reply	other threads:[~2006-03-22 22:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  6:23 Linus Torvalds
2006-03-20 12:02 ` 2.6.16.x will be a long-living kernel series Adrian Bunk
2006-03-20 12:05   ` Arjan van de Ven
2006-03-20 12:12     ` Adrian Bunk
2006-03-20 13:03       ` Arjan van de Ven
2006-03-24  0:22         ` Adrian Bunk
2006-03-20 19:22       ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04   ` Jeff Garzik
2006-03-20 19:25     ` Jan Engelhardt
2006-03-20 19:32       ` Joe Korty
2006-03-20 19:33       ` Linus Torvalds
2006-03-20 21:05         ` Andreas Schwab
2006-03-20 22:52         ` Matthias Andree
2006-03-22  5:22 ` Peter Williams
2006-03-22  6:31   ` Ashok Raj
2006-03-22 13:08     ` Ashok Raj
2006-03-22 13:25       ` Michal Piotrowski
2006-03-22 17:39       ` Rafael J. Wysocki
2006-03-22 17:54         ` Ashok Raj
2006-03-22 18:11           ` Rafael J. Wysocki
2006-03-22 18:27             ` Ashok Raj
2006-03-22 20:40               ` Rafael J. Wysocki
2006-03-22 21:00                 ` Ashok Raj
2006-03-22 21:36                   ` Rafael J. Wysocki
2006-03-22 22:27     ` Peter Williams [this message]
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09   ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01  9:18     ` netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error Adrian Bunk
     [not found] <5Sm46-2a7-13@gated-at.bofh.it>
     [not found] ` <5T455-7j-11@gated-at.bofh.it>
     [not found]   ` <5T5aR-1DN-23@gated-at.bofh.it>
     [not found]     ` <5Tbgl-2dp-43@gated-at.bofh.it>
2006-03-23  0:05       ` Linux v2.6.16 Bodo Eggert

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=4421CF5F.7010402@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®