home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news.service.uci.edu!ucivax!moe!kofax!lawnet!mbf!brian
- From: brian@mbf.UUCP (Brian Davis)
- Newsgroups: comp.unix.internals
- Subject: Re: Floating point emulation
- Message-ID: <181290@mbf.UUCP>
- Date: 9 Dec 92 16:10:04 GMT
- References: <1992Dec8.022408.16408@candle.uucp>
- Organization: MAI Systems Corp.
- Lines: 16
-
- In article <1992Dec8.022408.16408@candle.uucp> root@candle.uucp (Bruce Momjian) writes:
- >
- >Now, when I run a floating point computation in an endless loop, and use
- >the kernel profiling functions(prfstat, prfld, prfdc) to see what kernel
- >resources are being used to emulate floating point, I find that 'prfpr'
- >reports usage as almost 100% user.
- >
-
- Profiling data is collected during clock interrupts. Any code which
- executes at a higher interrupt priority than the clock will never show up
- in the profile. This is probably the case for the floating point
- emulation code.
- --
- Brian Davis It ain't no sin!
- MAI Systems Corp., Tustin, CA Take off your skin,
- brian%mbf.uucp@ics.uci.edu And dance around in your bones.
-