mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Jiri Kosina <jkosina@suse.cz>, Adam Osuchowski <adwol@zonk.pl>,
	linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Is 386 processor still supported?
Date: Thu, 8 Jan 2009 16:10:46 +0100	[thread overview]
Message-ID: <20090108151046.GK18120@elte.hu> (raw)
In-Reply-To: <20090108150448.2393aeb0@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > > Hmm. Where in Kconfig is SMP for M386 not allowed?
> > 
> > Dunno, kconfig is too much of a jungle for a simple person like me ;-)
> > 
> > But afaik i386 (and possibly i486) don't support nearly enough for a
> > modern SMP system.
> > 
> > Alan used to have i486-smp I think, one of the very few ever made.
> 
> The first systems that supported the Intel MP standard are 486 based 
> with external APIC. The prior systems used various proprietary MP 
> interfaces from the simple stuff in the Compaq (which Linux doesn't 
> support as Compaq refused to allow Thomas Radke to contribute it) to the 
> fairly extreme end of things with the Sequent boxes.
> 
> In addition our FPU emulation and some of our handling for x86 
> processors where we have to do the WP bit in software is also not SMP 
> safe.
> 
> So our minimal spec for SMP is probably 486DX + external Intel APIC.
> 
> In practice I doubt there is a single Intel APIC type 486 SMP box on the 
> planet running Linux (or quite possibly running at all)

yeah, that's very likely true. I think we could eliminate some of the SMP 
complications by requiring cmpxchg presence for CONFIG_SMP, agreed?

	Ingo

  reply	other threads:[~2009-01-08 15:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 12:03 Adam Osuchowski
2009-01-08 13:05 ` Jiri Kosina
2009-01-08 13:24   ` Cyrill Gorcunov
2009-01-08 13:48     ` Jiri Kosina
2009-01-08 14:13   ` Peter Zijlstra
2009-01-08 14:21     ` Jiri Kosina
2009-01-08 14:27       ` Peter Zijlstra
2009-01-08 15:04         ` Alan Cox
2009-01-08 15:10           ` Ingo Molnar [this message]
2009-01-13  1:06             ` Maciej W. Rozycki
2009-01-15 12:36               ` Jan-Benedict Glaw
2009-01-15 13:22                 ` Maciej W. Rozycki
2009-01-15 13:32                   ` Alan Cox
2009-01-15 14:15                     ` Maciej W. Rozycki
2009-01-15 14:17                       ` Ingo Molnar
2009-01-16  9:00                         ` Pavel Machek
2009-01-16 10:13                           ` Jan-Benedict Glaw
2009-01-16 11:18                           ` Andrey Panin
2009-01-16 13:46                           ` Ingo Molnar
2009-01-16 18:17                           ` H. Peter Anvin
2009-01-15 14:20                       ` Jan-Benedict Glaw
2009-01-15 14:37                         ` Bastien ROUCARIES
2009-01-15 14:25                       ` Alan Cox
2009-01-15 14:44                         ` Maciej W. Rozycki
2009-01-15 20:11                           ` H. Peter Anvin
2009-01-15 14:46                     ` Jan-Benedict Glaw
2009-01-08 16:45         ` Sam Ravnborg
2009-01-08 16:27   ` Andi Kleen

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=20090108151046.GK18120@elte.hu \
    --to=mingo@elte.hu \
    --cc=adwol@zonk.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®