From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
hpa@zytor.com, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Matthew Garrett <mjg59@google.com>,
Josh Boyer <jwboyer@redhat.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Steve Wahl <steve.wahl@hpe.com>,
Mike Travis <mike.travis@hpe.com>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Arnd Bergmann <arnd@arndb.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Giovanni Gherdovich <ggherdovich@suse.cz>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
Kees Cook <keescook@chromium.org>,
Martin Molnar <martin.molnar.programming@gmail.com>,
Pingfan Liu <kernelfans@gmail.com>,
jailhouse-dev@googlegroups.com
Subject: Re: [PATCH] x86/smpboot: Remove 486-isms from the modern AP boot path
Date: Thu, 2 Apr 2020 00:32:30 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2004012353100.4156324@eddie.linux-mips.org> (raw)
In-Reply-To: <beefca46-ac7c-374b-e80a-4e7c3af2eb2b@citrix.com>
On Wed, 1 Apr 2020, Andrew Cooper wrote:
> > Even though we supported them by spec I believe we never actually ran MP
> > on any 486 SMP system (Alan Cox might be able to straighten me out on
> > this); none that I know of implemented the MPS even though actual hardware
> > might have used the APIC architecture. Compaq had its competing solution
> > for 486 and newer SMP, actually deployed, the name of which I long forgot.
> > We never supported it due to the lack of documentation combined with the
> > lack of enough incentive for someone to reverse-engineer it.
>
> :)
>
> I chose "486-ism" based on what the MP spec said about external vs
> integrated Local APICs. I can't claim to have any experience of those days.
The spec is quite clear about the use of discrete APICs actually:
"5.1 Discrete APIC Configurations
" Figure 5-1 shows the default configuration for systems that use the
discrete 82489 APIC. The Intel486 processor is shown as an example;
however, this configuration can also employ Pentium processors. In
Pentium processor systems, PRST is connected to INIT instead of to
RESET."
:) And if in the way the internal local APIC in P54C processors can be
permanently disabled (causing it not to be reported in CPUID flags) via a
reset strap, e.g. to support an unusual configuration.
As I recall the integrated APIC would in principle support SMP configs
beyond dual (the inter-APIC bus was serial at the time and supported 15
APIC IDs with the P54C), but at the time the P54C processor was released
the only compatible I/O APICs were available as a part of Intel PCI south
bridges (the 82375EB/SB ESC and the 82379AB SIO.A). Those chips were not
necessarily compatible with whatever custom chipset was developed to
support e.g. a quad-SMP P54C system. Or there were political reasons
preventing them from being used.
Then the 82489DX used an incompatible protocol (supporting 254 APIC IDs
among others, and as I recall the serial bus had a different number of
wires even), so it couldn't be mixed with integrated local APICs. That's
why discrete APICs were sometimes used even with P54C processors.
And the 82093AA standalone I/O APIC was only introduced a few years
later, along with the Intel HX (Triton II) SMP chipset. I still have a
nice working machine equipped with this chipset and dual P55C processors
@233MHz. Even the original CPU fans are going strong. :) Its MP table is
however buggy and difficult to work with if the I/O APIC is to be used,
especially if PCI-PCI bridges are involved (there's none onboard, but you
can have these easily in multiple quantities on option cards nowadays).
Maciej
next prev parent reply other threads:[~2020-04-01 23:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 10:14 [PATCH] x86/smpboot: Remove 486-isms from the modern AP boot path Andrew Cooper
2020-03-25 10:17 ` hpa
2020-03-25 14:37 ` Thomas Gleixner
2020-03-31 23:35 ` Maciej W. Rozycki
2020-04-01 10:23 ` David Laight
2020-04-01 13:26 ` Maciej W. Rozycki
2020-04-01 22:30 ` Andrew Cooper
2020-04-01 23:32 ` Maciej W. Rozycki [this message]
2020-03-31 17:58 ` [PATCH v2] " Andrew Cooper
2020-03-31 22:23 ` Brian Gerst
2020-03-31 22:44 ` Andrew Cooper
2020-03-31 22:53 ` Brian Gerst
2020-04-01 9:22 ` Andrew Cooper
2020-04-01 11:39 ` Brian Gerst
2020-04-01 12:14 ` Andrew Cooper
2020-04-01 14:38 ` Brian Gerst
2020-04-01 14:47 ` Andrew Cooper
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=alpine.LFD.2.21.2004012353100.4156324@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=andrew.cooper3@citrix.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dhowells@redhat.com \
--cc=dimitri.sivanich@hpe.com \
--cc=ggherdovich@suse.cz \
--cc=hpa@zytor.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=jmorris@namei.org \
--cc=jwboyer@redhat.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.molnar.programming@gmail.com \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=mjg59@google.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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