The time that is left is the current emulation time, which is synchronized to realtime using high resolution clocks(depending on the system, the slowest and final(catch-all) usage being the SDL_Ticks() function for crude synchronization, compared to Windows and PSP's high resolution clocks).
This eventually gets added to the global time for CPU(and also hardware by extension, since their timings are based on the CPU timings provided). This amount of cycles is used by the emulator to (after addition like mentioned) convert to time spent on the instruction. This is the 8086/8088 source code, which load their cycles spent into CPU.cycles_OP(Which gets combined(added) with timings by the CPU core itelf, which handle hardware interrupts(IRQs) timings, Exceptions timings and Prefix timings to create the total time spent on the instruction(and other things like the IRQ and exception for the current instruction)).
Emu8086 simulator full#
The credits music sounds a bit better, but still not completely right though? The same applies to the Kefrens bar effect(although it's too small to see more when using the Direct Plot setting, which this current 2.0GHz CPU requires to even have a bit of speed(running at 30% of realtime speed, 100% speed is realtime(emulated CPU and hardware running at full speed, as by their requirements))). Now 8088 MPH gives me a percentage of 39%(accurate)? Although I didn't apply memory and I/O timings for different hardware yet. The algorithm instructions (DAA, DAS, AAA, AAS, AAM, AAD).Įdit: Found something that describes the timings:Įdit: Implemented those timings into the functionality that still needs them. The repeatable string instructions (MOVSB/W, STOSB/W, LODSB/W, SCASB/W). The flags set&clear instructions (STC, CLC, CMC, HLT etc.) Currently assumed 2 cycles for them.
Currently assumed the MOV SegReg, Mem instruction timings for them. Now most instructions have their timings implemented. I've modified my 8086 emulation core to use the timings as specified in the document ( … tion_Timing.PDF ).
0 kommentar(er)
