Hi all, quick question regarding atomic memory. I'm using the starter_se.py config script (gem5/configs/example/arm/) and with memory mode being atomic. For what I understood, using atomic memory mode should provide the data irregardless of its position in memory(L1, L2 or off-chip mem) within the next (simulation) clock cycle. When running a simple program and exporting the traces at a cpu frequency of 1GHz and 500MHz, I assumed the tick-count to be equal, meaning 1GHz would finish at half the time of the 500MHz. To my surprice it didn't, leading me to believe there are some other system dependencies running at a different frequency. Does anyone know what that might be, or any clue what causes these different runtimes? I tried setting the system frequency to match the clock frequency aswell, with the same result. I ended up with a factor of 1.24 more ticks in the 500MHz simulation.
Thanks in advance, Øivind Harket Bakke _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
