From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Robert Love <rml@tech9.net>,
Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: Wed, 12 Jun 2002 08:22:47 -0700 [thread overview]
Message-ID: <20020612152247.GH22961@holomorphy.com> (raw)
In-Reply-To: <1023820116.22156.271.camel@sinai> <3215445436.1023869217@[10.10.2.3]>
On Wed, Jun 12, 2002 at 08:06:58AM -0700, Martin J. Bligh wrote:
> Indeed. And before that gets changed, it would be necessary
> to change the bootstrap procedure not to crash if you have
> more than NR_CPUS cpus (as Andrew reported it did), but instead
> to just not configure them ... much less troublesome.
> M.
There are also fun deadlocks on i386 with "too many cpu's" as it
appears the kernel attempts to use logical APIC mode to get beyond
the eigth cpu and seems unaware that it can't IPI them that way unless
it's configured to always use the clustered hierarchical destination
format, though that's perhaps a little beyond just NR_CPUS. Perhaps
some kind of sanity checking is needed at the arch level for issues
like this as well, not just the absolute maximum number of cpu's?
Cheers,
Bill
next prev parent reply other threads:[~2002-06-12 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 17:52 [PATCH] CONFIG_NR_CPUS, redux Robert Love
2002-06-11 18:09 ` Randy.Dunlap
2002-06-11 18:19 ` Robert Love
2002-06-11 18:21 ` Ruth Ivimey-Cook
2002-06-11 18:28 ` Robert Love
2002-06-12 1:36 ` jw schultz
2002-06-12 15:06 ` Martin J. Bligh
2002-06-12 15:22 ` William Lee Irwin III [this message]
2002-06-11 18:29 ` Martin Dalecki
2002-06-11 23:20 ` Dave Jones
2002-06-13 8:51 ` Helge Hafting
2002-06-19 11:53 ` Bill Davidsen
2002-06-11 20:10 ` Rob Radez
-- strict thread matches above, loose matches on Subject: below --
2002-06-12 3:29 Matt_Domsch
2002-06-12 4:13 ` Austin Gonyou
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=20020612152247.GH22961@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rml@tech9.net \
/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