Hi Leonardo,
The DPRINTFs print time in ticks (a representation of absolute time,
independent of any modules clock speed). By default the unit is 1 tick = 1 ps.
I don’t know if you are trying to track the incoming requests, or the
reads/writes to the DRAM. If you are doing the former, why not use the
CommMonitor between the membus and the DRAM? If you are doing the latter, a
word of caution. The DRAM model is event-based and actions may be scheduled and
executed “out of order". Hence, you should also consider when the read and
write is actually scheduled to happen and not just when the decision is taken.
Andreas
From: Leonardo Ecco <[email protected]<mailto:[email protected]>>
Reply-To: gem5 users mailing list
<[email protected]<mailto:[email protected]>>
Date: Friday, 7 February 2014 13:35
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [gem5-users] DRAM Memory traces
Hello,
I'm using GEM5 to collect DRAM memory access traces. I'm running an
out-of-order model of ARM with the classic memory (enabled L1 and L2 caches),
and using DPRINTF statements inside the DRAM model.
The output I'm getting is something like this:
1775299000: system.physmem: Memory request of 32 bytes for address: WRITE 96400
1775436000: system.physmem: Memory request of 32 bytes for address: READ 903e0
1775492000: system.physmem: Memory request of 32 bytes for address: READ 923e0
1775523000: system.physmem: Memory request of 32 bytes for address: WRITE 8e3e0
1775598000: system.physmem: Memory request of 32 bytes for address: READ 96400
1776024000: system.physmem: Memory request of 32 bytes for address: READ 983e0
1776055000: system.physmem: Memory request of 32 bytes for address: WRITE 903e0
1776131000: system.physmem: Memory request of 32 bytes for address: READ 903e0
1776162000: system.physmem: Memory request of 32 bytes for address: WRITE 943e0
1776197500: system.physmem: Memory request of 32 bytes for address: READ 92400^C
My question is what does the numbers on the left mean. Are those simulation
cycles (and if so, is that measured according to the system clock or the
processor clock)? Or are they actually time (perhaps measured in nanoseconds)?
Thanks in advance.
-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered
in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
Registered in England & Wales, Company No: 2548782
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
