Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!rex!ames!sgi!calcite!vjs
From: vjs@calcite.UUCP (Vernon Schryver)
Newsgroups: comp.unix.i386
Subject: Re: Pic on ISC's 386/ix 2.0.2 locks system hard.
Message-ID: <78@calcite.UUCP>
Date: 30 Nov 89 16:37:03 GMT
References: <1989Nov28.075243.10363@pcrat.uucp> <1708@mtunb.ATT.COM>
Organization: Rhyolite Software, Mountain View, CA
Lines: 18

In article <1708@mtunb.ATT.COM>, jcm@mtunb.ATT.COM (John McMillan) writes:
> 	On an ATT-6386 running SVR3.2, the 387 problem is 'fixed' by adding
> 	the following to '/etc/conf/cf.d/stune' and re-building the kernel:
> 
> DO387CR3	1
> 
> john mcmillan -- att!mtunb!jcm -- muttering for SELF... not THEM

Can someone say precisely what the kernel work-around is?  I've heard
of something like leaving the 387 marked absent or in other words continueing
to "emulate" 387 instructions, and in the "emulator" doing strange and
slow stuff before actually doing the ESC+etc.  How much slower is
<old 386>+<software fix>+387 than <new 386>+387?   How many cycles are
added to each 387 operation?


Vernon Schryver
vjs@calcite.uucp