From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: fisher@sgi.com
Cc: linux@hollywood.engr.sgi.com, fisher@hollywood.engr.sgi.com
Subject: Re: Pentium F00F bug Linux workaround; BSDI Response
Date: Mon, 17 Nov 1997 15:23:46 -0800 [thread overview]
Message-ID: <199711172323.PAA27334@dm.cobaltmicro.com> (raw)
In-Reply-To: <199711172128.NAA04775@hollywood.engr.sgi.com> (fisher@hollywood.engr.sgi.com)
I'm going to choose more lightly what I decide to post here if it's
going to make it's way to every tom, dick, and harry out there in the
unix industry...
Fact is that Intel was trying to make sure _no_ vendor had a fix out
before anyone else. If it was not explicitly stated in the NDA they
signed with Intel, this was a mistake and not what was intended.
Now that you've talked to Borman about this fish, ask him why he had
to take the patch set down within a day or so. If he says "because it
was a BETA patch set", I'd find his response hard to believe.
Intel engineers internally were working themselves on fixes for
various systems that they did have source to (Linux, maybe
{net,free}BSD and a few others) and planned to release those patch
sets and allow vendors to release their own patches at the same exact
time.
BSDI putting out their patch ahead of that point in time was, if
anything, totally against how Intel wanted things happen.
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1997-11-17 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-17 21:28 Pentium F00F bug Linux workaround; BSDI Response William Fisher
1997-11-17 21:28 ` William Fisher
1997-11-17 23:23 ` David S. Miller [this message]
1997-11-17 23:56 ` Alan Cox
1997-11-17 23:56 ` 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=199711172323.PAA27334@dm.cobaltmicro.com \
--to=davem@dm.cobaltmicro.com \
--cc=fisher@hollywood.engr.sgi.com \
--cc=fisher@sgi.com \
--cc=linux@hollywood.engr.sgi.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 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.