Mahmood,
I have comfirmed that sleep() function executes. Besides that,
simulation execution on host machine takes longer but execution time
value (sim_seconds) in stat file does not show a significant difference.
Alinti Mahmood Naderan mahmood...@gmail.com
Sanem,
maybe you put sleep()
That is a normal thing. sim_second is a workload related parameter
while simulation execution on the host is related to your host, e.g
wall time.
Assume you are simulating single core at 2GHz frequency. As a result
simulating 1 second of your workload takes 2*10^9 cycles. If you write
a good code
The sleep is delaying the simulator, NOT the simulation,
If you want the simulated workload to take longer you have to figure out how to
stall the cpu.
Playing with cache latencies should do the trick.
De: gem5-users-boun...@gem5.org
Actually I am not dealing with sleep() function. I have put some codes
to the cache structure and I can not figure out the performance
overhead of my added codes by looking execution time in stat file!
Playing with cache latencies or changing blk-whenReady value do not
affect the
