Hi guys,

I'm am running the PARSEC benchmark suite on gem5 ARM in full system
simulation mode. For some reason it seems like some m5 PseudoInst
(checkpoint, stats_reset, stats_dump) are executed twice and I'm not sure
why.

I built PARSEC on QEMU following this guide
<https://github.com/arm-university/arm-gem5-rsk/wiki>. I'm running the
benchmarks single-threaded.

In the beginning of each PARSEC benchmark's ROI there is an m5 checkpoint
command and a reset stats command. On exiting the ROI there is a dump stats
command.

When simulating the the code with gem5 I get the following sequence of m5
commands:
checkpoint, reset stats, checkpoint, reset stats, ...(ROI running)..., dump
stats, dump stats.
I'm expecting: checkpoint, reset stats, ...(ROI running)..., dump stats.

However, the simulated application has the correct output (prints from the
simulated program's ROI occur once).

Any ideas why this is happening?

Can provide logs for Parsec and m5 and building / running commands.

Thanks, David
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to