From owner-freebsd-hackers Thu Nov 13 11:57:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14045 for hackers-outgoing; Thu, 13 Nov 1997 11:57:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14035 for ; Thu, 13 Nov 1997 11:57:41 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id OAA08389; Thu, 13 Nov 1997 14:57:45 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Thu, 13 Nov 1997 14:57:45 -0500 (EST) From: "David E. Cross" To: Terry Lambert cc: "Ron G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: BSDI F0 bug workaround implementation In-Reply-To: <199711131907.MAA28899@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 13 Nov 1997, Terry Lambert wrote: > Only the first 7 IDT entries are affected (at least in the Linux > workaround), not the whole table. > > On the minus side, the impact *is* non-zero. > > Like the FPU bug, since a workaround exists, it's likely to be swept > under the software as well. 8-(. > Yes, but Interupts are called much more frequently than floating-point instructions. I for one am going to email my intel representative and ask for a replacement... I think that it would be in intel's best interest to handle this with as little fuss as possible. -- David Cross ACS Consultant