Hi Giacomo,
Indeed, I was able to use ArmMMU.connectWalkerPorts method and run the config
file in fs mode.
However, I a, still struggling with the segmentation fault in se mode.
Does it make any sense to have a config file working in fs mode but failing in
se? (notice that it is running in both
> -Original Message-
> From: Ali Ghandour via gem5-users
> Sent: 12 October 2021 08:50
> To: gem5-users@gem5.org
> Cc: Ali Ghandour
> Subject: [gem5-users] Re: Porting a configuration file from gem5 v20 to gem5
> v21
>
> Hi Giacomo,
>
> Indeed, I was able to use ArmMMU.connectWalkerPort
I would suggest using DPRINTF instead of cout. It's possible that some
print statements aren't being flushed.
Jason
On Mon, Oct 11, 2021 at 7:16 AM Sampad Mohapatra wrote:
> Hi Jason,
>
> I have added a std::cout statement to the resetstats()'s body and I am
> calling m5_reset_stats from my GPU
I see. Thanks for the clarification. Will see if DPRINTF works, otherwise
will write to a file, which should be ok as I am calling m5_stat_reset only
once.
On Tue, Oct 12, 2021 at 10:57 AM Jason Lowe-Power
wrote:
> I would suggest using DPRINTF instead of cout. It's possible that some
> print st
Thank you, it is resolved!
I forgot this line
`system.workload = SEWorkload.init_compatible(binary)`
On Fri, Oct 8, 2021 at 4:19 PM Gabriel Busnot via gem5-users <
gem5-users@gem5.org> wrote:
> Hi,
>
> 1 and 2 or inoffensive warnings. To solve 3, can you please compile
> gem5.debug and provide us
