Hi Mohammad,
I updated the CommMonitor some time ago to make it use the new probe interface
instead of bundling all analyses within the monitor itself. This means that you
need to hook up a memory trace probe to the monitor to get a memory trace.
There is a separate probe for stack distances that you can use if you're
interested in stack distances distributions. I have updated the wiki to reflect
this change.
What you need to do nowadays is something along these lines:
self.monitor = CommMonitor()
self.dcache_port = self.monitor.slave
self.monitor.master = dc.cpu_side
self.monitor.trace = MemTraceProbe(trace_file="my_trace.trc.gz")
Regards,
Andreas
On 05/10/2015 02:21, "gem5-users on behalf of Mohammad Alian"
<[email protected]<mailto:[email protected]> on behalf of
[email protected]<mailto:[email protected]>> wrote:
Hi all,
In the latest gem5 dev version, I tried to add a CommMonitor object based on
the instructions on
http://www.gem5.org/General_Memory_System#Tracing_and_traffic_generation. But
"trace_file" option is no longer exists in the CommMonitor class. gem5 runs
with the following code but I cannot get any trace. How should I make this
work? Any help is appreciated.
self.monitor = CommMonitor()
self.dcache_port = self.monitor.slave
self.monitor.master = dc.cpu_side
Thank you,
Mohammad
________________________________
-- 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.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
