I tried the example script simpoints-se-restore.py.
I found a strange outcome.
Given SimPoint information with 1000000 simpoint_interval.
board.set_se_simpoint_workload(
binary=obtain_resource("x86-print-this"),
arguments=["print this", 15000],
simpoint=SimpointResource(
simpoint_interval=1000000,
simpoint_list=[2, 3, 4, 15],
weight_list=[0.1, 0.2, 0.4, 0.3],
warmup_interval=1000000,
),
checkpoint=obtain_resource("simpoints-se-checkpoints-v23-0-v1"),
)
Additionally, the warmup and starting from simpoint begin procedure is
shown below. It said that the stats would be reset.
src/sim/simulate.cc:194: info: Entering event queue @ 764242326. Starting
simulation...src/sim/simulate.cc:194: info: Entering event queue @ 1390004448.
Starting simulation...
warn: No behavior was set by the user for simpoint begin. Default behavior is
resetting the stats and continuing.
src/sim/simulate.cc:194: info: Entering event queue @ 1390004448.
Starting simulation...
src/sim/simulate.cc:194: info: Entering event queue @ 2007685281.
Starting simulation...
However, according to the lines after the second Begin Simulation Statistics in
stats.txt:
simSeconds:0.000000
simTicks:2085
simInsts:2000004
Do you think that three items have something wrong?
I think the simInsts should be 1000000, simTicks should be (2007685281
- 1390004448), simSeconds should larger than 0.0 sec_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
