[gem5-users] Re: Memory traces using CommMonitor

2023-02-16 Thread Ayaz Akram via gem5-users
Hi Sadhana, SE mode, by default, uses a 4KB page size. You can convert the pkt addresses generated by the commMonitor to page addresses manually or change the commMonitor code to dump the page addresses. -Ayaz On Wed, Feb 15, 2023 at 9:08 PM Sadhana . wrote: > Hai Ayaz, > In addition to the

[gem5-users] Re: Memory traces using CommMonitor

2023-02-15 Thread Sadhana . via gem5-users
Hai Ayaz, In addition to the previous query, is it possible to determine the page size supported during the simulation in SE mode. I understood that the commMonitor generates the physical address. Whether my understanding is correct. Since address length varies, I had doubts regarding this page

[gem5-users] Re: Memory traces using CommMonitor

2023-02-14 Thread Sadhana . via gem5-users
Thank you. On Tue, Feb 14, 2023 at 4:34 PM Ayaz Akram wrote: > 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

[gem5-users] Re: Memory traces using CommMonitor

2023-02-14 Thread Ayaz Akram via gem5-users
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