adjust CLOCK_CYCLES and related macros to handle fpu/iu concurrency
add CLOCK_CYCLES_FPU, which does exactly what CLOCK_CYCLES already did. add CONCURRENCY_CYCLES, which sets fpu_cycles, which is the number of available concurrent execution cycles that the integer unit can do "free" work in while the fpu is executing. adjust CLOCK_CYCLES so that if there are fpu_cycles, the cycle count is subtracted from fpu_cycles instead of cycles, emulating the behavior of these concurrent cycles being "free" as on real hardware.
This commit is contained in:
@@ -267,9 +267,22 @@ static void prefetch_flush()
|
||||
|
||||
|
||||
#define OP_TABLE(name) ops_ ## name
|
||||
#define CLOCK_CYCLES(c) cycles -= (c)
|
||||
#define CLOCK_CYCLES(c) \
|
||||
{\
|
||||
if (fpu_cycles > 0) {\
|
||||
fpu_cycles -= (c);\
|
||||
if (fpu_cycles < 0) {\
|
||||
cycles += fpu_cycles;\
|
||||
}\
|
||||
} else {\
|
||||
cycles -= (c);\
|
||||
}\
|
||||
}
|
||||
#define CLOCK_CYCLES_FPU(c) cycles -= (c)
|
||||
#define CONCURRENCY_CYCLES(c) fpu_cycles = (c)
|
||||
#define CLOCK_CYCLES_ALWAYS(c) cycles -= (c)
|
||||
|
||||
|
||||
#include "386_ops.h"
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user