Hi Sadhana, I think the first number is the requestor port id (IIRC). The above trace should have all requests to the main memory as your CommMonitor is connected between the membus and MemCtrl (and all memory traffic should go through it).
-Ayaz On Mon, Feb 13, 2023 at 7:52 PM Sadhana . via gem5-users < gem5-users@gem5.org> wrote: > I am using gem5 for generation of memory traces. While going through gem5 > videos I found a method to generate traces using commMonitor. I have > modified the code as follows: > system.comm_monitor=CommMonitor() > system.comm_monitor.cpu_side_port=system.membus.mem_side_ports > > system.comm_monitor.trace=MemTraceProbe(trace_file=f"mem_trace",trace_compress=True) > #system.system_port = system.membus.slave > system.mem_ctrl=MemCtrl() > system.mem_ctrl.dram = DDR3_1600_8x8() > system.mem_ctrl.dram.range = system.mem_ranges[0] > #system.mem_ctrl.port = #system.membus.mem_side_ports > system.mem_ctrl.port = system.comm_monitor.mem_side_port > system.system_port = system.membus.cpu_side_ports > I am running SE mode using arm ISA. I have got the traces as well: > 7,r,980,4,256,0 > 7,r,984,4,256,77000 > 7,r,988,4,256,126000 > 8,r,474576,4,10,175000 > 7,r,992,4,256,238000 > 7,r,996,4,256,287000 > 8,w,474576,4,10,336000 > 7,r,1000,4,256,357000 > 8,w,474572,4,10,406000 > 7,r,1004,4,256,427000 > 8,r,1028,4,10,476000 > 7,r,1008,4,256,525000 > 8,w,474568,4,10,574000 > Now my doubt is what does port number 7,8 mean. should I consider the > entire trace as a memory trace? I want only traces of the main memory. > > > > > Thanks and Regards, > Sadhana, > Research Scholar-NITK, > Dept. of Computer Science and Engineering > . > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
