From: James Bottomley <James.Bottomley@SteelEye.com>
To: Kurt Garloff <garloff@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP on assym. x86
Date: Wed, 21 Mar 2001 14:13:15 -0500 [thread overview]
Message-ID: <200103211913.OAA02121@localhost.localdomain> (raw)
> recently upgrading one of my two CPUs, I found kernel-2.4.2 to be
> unable to handle the situation with 2 different CPUs (AMP =3D
> Assymmetric multiprocessing ;-) correctly. Some details on my system:
> Dual BX board (DFI P2XBL/D), iPII 350 (Deschutes) + iPIII 850
> (Coppermine) Note: The difference in features is the XMM (SSE) flag.
> The problems are twofold (a) Determination of the correct common
> features (=3D: COMCAP), i.e.
> boot_cpu_data.x86_capaility[0] at the correct time (b) TSC stuff
I have similar problems. I've got a reconfigurable non-APIC 8 way system with
(currently) 4 p5-66 and 4 p5-166 processors. I found the answer to (b) was
simply to disable the TSC stuff---my processors aren't even guaranteed to be
fed from the same clock, so there's no hope for TSC coherency.
I run into your problem (a) when trying a mixture of 486 and 586 processors.
The simplest work around I find is just to make sure that the boot CPU has the
lowest capability set (i.e. boot off a 486). Could you just swap the order of
your processors to achieve the same effect?
James Bottomley
next reply other threads:[~2001-03-21 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 19:13 James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:55 SMP on assym. x86 Kurt Garloff
2001-03-21 16:32 ` Mark Hahn
2001-03-21 23:41 ` Alan Cox
2001-03-22 12:00 ` Kurt Garloff
2001-03-22 13:48 ` Mark Hahn
2001-03-23 10:19 ` Eric W. Biederman
2001-03-21 17:16 ` Linus Torvalds
[not found] ` <99anl4oi@penguin.transmeta.com>
2001-03-22 13:20 ` Pavel Machek
2001-03-23 10:18 ` Kurt Garloff
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=200103211913.OAA02121@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.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