From owner-freebsd-hackers Sun Jul 2 2:57:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id C7E5137BC2C; Sun, 2 Jul 2000 02:57:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA01299; Sun, 2 Jul 2000 11:57:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: hackers@FreeBSD.ORG, KATO Takenori , Mike Smith Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 23:47:05 PDT." <200007020647.XAA33812@john.baldwin.cx> Date: Sun, 02 Jul 2000 11:57:36 +0200 Message-ID: <1297.962531856@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007020647.XAA33812@john.baldwin.cx>, John Baldwin writes: >*ahem* You might want to read the first paragraph as well. It is >for situations where one _can't_ update one's BIOS. I don't see why >making it a tweakable kernel compile time know that is off by >default would be so incredibly bad. We have precedents already for >this type of thing. And yes, in this case, the CPU is not performing >as advertised. So far we have set the limit at hardware being used correctly. Either way, this patch was not the correct way to fix this particular erratum. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message