From owner-freebsd-hackers Mon Jul 3 22:49:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id E691037C112 for ; Mon, 3 Jul 2000 22:49:28 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 67527 invoked by uid 1000); 4 Jul 2000 05:49:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Jul 2000 05:49:27 -0000 Date: Tue, 4 Jul 2000 00:49:27 -0500 (CDT) From: Mike Silbersack To: Mike Smith Cc: KATO Takenori , hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-Reply-To: <200007040153.SAA00477@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Jul 2000, Mike Smith wrote: > > Mike Smith wrote: > > > > > If it's something that can be done as eg. a KLD > > > we might want to do that instead, or through some other mechanism for > > > handling these sort of CPU quirks. > > > > It sounds good. If binary-format quriks is supported, we can supply > > update modules for new CPU and newly found errata like the update > > module for AMD K6-2 CPU of Windows 95. > > Indeed. This won't help us where we need to modify the actual behaviour > of a system component, but when we can perform external corrective > actions, it will help a lot. I don't understand the idea here. Are you going to have a KLD that patches the kernel? If so, you'd have to make world before it'd become active, in which case rebuilding the kernel would be quicker. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message