From: Andi Kleen <ak@muc.de>
To: "Tommy Faasen" <tommy@vuurwerk.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP processor rework help needed
Date: 14 Oct 2001 22:33:27 +0200 [thread overview]
Message-ID: <k2wv1yhsh4.fsf@zero.aec.at> (raw)
In-Reply-To: <000b01c154ee$1d6a2610$6400a8c0@it0>
In-Reply-To: "Tommy Faasen"'s message of "Sun, 14 Oct 2001 22:23:37 +0200"
In article <000b01c154ee$1d6a2610$6400a8c0@it0>,
"Tommy Faasen" <tommy@vuurwerk.nl> writes:
> Hi,
> I have this unique situation where cpu 1 has less features (like fxsr) then
> cpu 0.
I used to have such an AMP machine too: a dual PII-300 with one Katmai and one
Deschutes. It's technically a violation of the specs; the Intel SMP spec
requires that the non boot cpus need to have a superset of the features
of the boot CPU. One CPU died, so it is symmetric now.
For most capabilities it should already work in 2.4 after hpa's cpu
set rewrite, but FXSAVE is unfortunately a bit of a special case because
it is used in the scheduler context switch and that is required early
in the initialization for SMP bootup and changing it would be very
intrusive.
In the 2.2 SuSE kernel it was fixed instead by adding a new kernel
command line option nofxsave that overrides the FXSAVE bit on the first
CPU. That is ok because such setup is very rare and is only generated by
people who build their own boxes; and these should also know how to pass
kernel command line arguments.
Such an option should also be easy to add to 2.4.
-Andi
next prev parent reply other threads:[~2001-10-14 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 20:23 SMP processor rework help needed Tommy Faasen
2001-10-14 20:33 ` Andi Kleen [this message]
2001-10-14 20:50 ` Gerhard Mack
2001-10-14 21:07 ` Andi Kleen
2001-10-15 15:20 ` Eric W. Biederman
2001-10-14 22:09 ` Tommy Faasen
2001-10-15 5:07 ` Pascal Schmidt
2001-10-15 21:25 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2001-10-15 17:16 Manfred Spraul
2001-10-15 21:39 ` Alan Cox
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=k2wv1yhsh4.fsf@zero.aec.at \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tommy@vuurwerk.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.