 |
Each simulation point has an execution weight
indicating what percentage of the overall program execution that SimPoint
represents. The simulation points are different than those listed in
the ASPLOS paper, since they were derived with a newer version of our toolkit
and with different SimPoint parameters. |
|
The interval size used to
create these simulation points are 10 and 100 million execution instructions.
Each simulation point provided is given as the number of the intervals from
the start of execution. The first interval of execution is indicated by a
Simulation Point of 0 (this is an important change from SimPoint 2.0). For example,
if the Simulation Point is 90, then you start simulating at instruction 90 *
100 million (9 billion) and stop simulating at instruction 9.1 billion
assuming a 100 million interval size was used to create the simulation
points. |
|
Also given for each Simulation Point is the
PC of the executed instruction that started that interval to be simulated.
You then only need to fast-forward until that instruction PC is encountered
the number of times shown in the last column (xBB). Then start
simulating for the interval length of instructions. Using the simulation point
starting PC and execution count is the recommended approach for using SimPoint. |
|
Note that if a point has PC==0
and executed == 0 this means that it is
the first interval of execution and the simulation interval starts at the
first instruction executed. |
