[gem5-users] Re: Can we use our own debug flags in fs mode?

Hi Gabe, Thanks for the reply. I guess prefetcher is varying the output every time. Am I right?. Regarding the debug flags, the code works perfectly in SE mode, even in FS mode if I don't specify any flag it runs fine. The problem comes only if I specify any flag. If I specify an already

[gem5-users] Re: Can we use our own debug flags in fs mode?

You can use your own debug flags in FS mode. The stats should mostly be deterministic, particularly in FS mode, but if the simulation interacts with something else that's not deterministic, like if you type on its console or it runs system calls on the host in SE mode, then things can change from

[gem5-users] Re: Benchmark terminating early

SE I suppose? It seems that the benchmark ends normally with an exit syscall, I would start by looking at --debug-flags SyscallBase to double check that. Then if that is the case, the only explanation is that some value is getting corrupted somewhere due to a gem5 bug. So I would try to: 1)

[gem5-users] Re: Memory -Address -Gem5-O3

Thanks Patel for your email. But I want to change in the source code because I want to find the address for the load instruction followed by specific instruction. Do you know where in gem5 should I make the changes? For instance, I want to know the memory addresses of every LD instruction

[gem5-users] Re: Memory -Address -Gem5-O3

Hi Alrhman, Look into the protocol state machine, say L1cache state machine. More specifically you can modify the mandatory_queue_in code for your requirement. The sequencer puts the CPU request into mandatory queue. Revert incase of any query. Regards, Vipin On Mon, 13 Jul, 2020, 01:18 ABD

[gem5-users] Re: Memory -Address -Gem5-O3

Thanks Carlos for your help. But I want to change in the source code because I want to find the address for the load instruction followed by specific instruction. Do you know where in gem5 should i make the changes ? Thanks From: Francisco Carlos via

[gem5-users] Re: Infinite loop in memory controller

Hi Taiyu, Looks like you have a single memory controller with 2 ranks instantiated. * The log flags labeled system.mem_ctrls are for general controller messages * The log flags labeled system.mem_ctrls_0 relate to rank 0 specific info * The log flags labeled system.mem_ctrls_1 relate

[gem5-users] Re: Memory -Address -Gem5-O3

hello Abd, You can see a similar output by enabling the Exec debug-flag. I would suggest you look at the gem5 documentation to further details in the debug-flags available and how to use them.

[gem5-users] Re: Memory -Address -Gem5-O3

You can get the output you are looking for by using --debug-flag=Exec and --debug-file=[file you want to write to] Also you may find --debug-start and --debug-end useful for you On Mon, Jul 13, 2020 at 12:04 PM ABD ALRHMAN ABO ALKHEEL via gem5-users < gem5-users@gem5.org> wrote: > Hi All, > >

[gem5-users] Re: Memory -Address -Gem5-O3

Hi All, Which file in gem5 prints the following output? I want to find the memory address for each instruction. Any help would be appreciated. [cid:eb12e102-62a0-40c1-90a3-38629a58b9fc] From: ABD ALRHMAN ABO ALKHEEL Sent: Sunday, July 12, 2020 7:46 PM To: