From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
andrea@suse.de (Andrea Arcangeli),
dledford@redhat.com (Doug Ledford),
paubert@iram.es (Gabriel Paubert),
mingo@redhat.com, gareth@valinux.com,
linux-kernel@vger.kernel.org
Subject: Re: missing mxcsr initialization
Date: Fri, 27 Oct 2000 12:42:03 +0100 (BST) [thread overview]
Message-ID: <E13p7te-0004MB-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10010262229330.864-100000@penguin.transmeta.com> from "Linus Torvalds" at Oct 26, 2000 10:35:25 PM
> Go back. Read ym email. Realize that you do this ONCE. At setup time.
(I've got about 2000 to read after this jaunt so I may have missed some)
> You can even split SEP into SEPOLD and SEPNEW, and _always_ just test one
> bit. You should not have to test stepping levels in normal use: that
> invariably causes problems when there are more than one CPU that has some
> feature.
Agree
> if (vendor == intel && stepping < 5) {
> ...
> }
>
> and it appears to work again, until it turns out that Cyrix has the same
> issue, and then it ends up being the test from hell, where different
> vendor tests all clash, and it gets increasingly difficult to add a new
> thing later on sanely.
And you end up with mtrr.c
> No thank you. We'll just require fixed feature flags. Which can be turned
> on as the features are enabled.
That seems sensible
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10010260835340.2335-100000@penguin.transmeta.com>
2000-10-27 0:39 ` Alan Cox
2000-10-27 5:35 ` Linus Torvalds
2000-10-27 11:42 ` Alan Cox [this message]
2000-10-27 19:07 ` H. Peter Anvin
[not found] <20001026021731.B23895@athlon.random>
2000-10-27 1:15 ` Alan Cox
2000-10-27 7:34 ` H. Peter Anvin
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=E13p7te-0004MB-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=dledford@redhat.com \
--cc=gareth@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paubert@iram.es \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®