public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: SMP on assym. x86
Date: 21 Mar 2001 09:16:20 -0800	[thread overview]
Message-ID: <99anl4$8oi$1@penguin.transmeta.com> (raw)
In-Reply-To: <20010321165541.H3514@garloff.casa-etp.nl>

In article <20010321165541.H3514@garloff.casa-etp.nl>,
Kurt Garloff  <garloff@suse.de> wrote:
>
>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.

This is not really a configuration Linux supports. You can hack it to
work in many cases, but I'm generally not inclined to make this a an
issue for me because:

 - intel explicitly doesn't support it necessarily even in hardware.
   You're supposed to only mix CPU's of the same stepping within a
   family, never mind different families.  They sometimes explicitly say
   which steppings are compatible and can be mixed.

   NOTE! For all I know, this might, for all I know, actually be due to
   fundamental issues like cache coherency protocol timing or similar.
   Safe answer: just say no.

 - The boot CPU under Linux is special, and will be used to determine
   things like support for 4M pages etc. It will then re-write the page
   tables to be more efficient. If the other CPU's don't support all the
   features the boot CPU has, they'll have serious trouble booting up. 

   NOTE! I'm not all that interested in trying to complicate the bootup
   logic to take into account all the differences that can occur.
   Especially as it only happens on arguably very broken hardware that
   doesn't meet the specs anyway.

So I'm perfectly happy with you fixing it on your machine, but right now
I have no incentives to make this a "real" option for a standard kernel.

I retain the right to change my mind, as always. Le Linus e mobile.

		Linus

  parent reply	other threads:[~2001-03-21 17:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [not found] ` <99anl4oi@penguin.transmeta.com>
2001-03-22 13:20   ` Pavel Machek
2001-03-23 10:18     ` Kurt Garloff
  -- strict thread matches above, loose matches on Subject: below --
2001-03-21 19:13 James Bottomley

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='99anl4$8oi$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --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