From owner-freebsd-stable Sun Oct 29 13:36:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id A862137B479 for ; Sun, 29 Oct 2000 13:36:17 -0800 (PST) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.0/8.11.1) with ESMTP id e9TLaHf20400 for ; Sun, 29 Oct 2000 13:36:17 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.11.0/8.11.0) with ESMTP id e9TLaHK64109 for ; Sun, 29 Oct 2000 13:36:17 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.11.0//ident-1.0) id e9TLaGx12311; Sun, 29 Oct 2000 13:36:16 -0800 (PST) Message-ID: <39FC984F.48AA97AD@quack.kfu.com> Date: Sun, 29 Oct 2000 13:36:15 -0800 From: Nick Sayer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: F00F-HACK still necessary? References: <200010291602.e9TG25B01059@cwsys.cwsent.com> <200010291843.e9TIhJG15929@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jdp@polstra.com wrote: > > In article <200010291602.e9TG25B01059@cwsys.cwsent.com>, Cy Schubert - > ITSD Open Systems Group wrote: > > > NO_F00F_HACK is only effective with the original Pentium. If you > > define i686_CPU, NO_F00F_HACK is implied. > > Close, but not quite right. If you _don't_ define I586_CPU then > NO_F00F_HACK is implied. Even if the code is in the kernel, it's not actually activated unless a Pentium is installed, though. So the only time you really need it is when you have an Intel Pentium that you know is NOT affected by the bug... Right? I mean apart from the few hundred bytes of code space, if the handler isn't installed, it's as if NO_FOOF_HACK was in there all along. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message