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
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
