Hi Javed,
Woops, I didn't see the split option in your first post. My bad.
I think the l2 is actually named "system.cpu0.l1i.downstream_destinations" and
you will find it in the ini file. I think this is due to the way gem5 sets
SimObject names. When you assign a SimObject to several object att
Hi Gogineni,
If you REALLY CAN'T modify the app, I would then replace the file(s) your app
opens with a symlink to the file you want to open.
And if you feel in a hacky mood, you can dive in src/sim/syscall_emul.hh and
hardcode path override in openatFunc. Needless to say this is a terrible lon
Hi Gabriel
Many thanks for your insight and input.
I have taken on board your suggestion and simplified the customisation of
CHI.py and CHI_config.py by just using the CHI_Config.CHI_RNF() class object
and adding another method to CHI_Config.CHI_RNF(), called addSharedL2Cache.
Also I have star
Hi Majid,
Out of curiosity, are you sure the configuration is the same? Could you try to
rebuild the bootloader in system/arm/bootloader/arm64 and make sure the config
script is pointing to it?
(Either with M5_PATH or by using the --bootloader option)
Please let me know if this works
Kind Rega
I'm trying to port maddpg on top of gem5
Here's my process:
First I've downloaded the maddpg from open ai:
https://github.com/openai/maddpg (I've also installed all the dependencies
for maddpg on the multi-particle environment)
In the next step, I used the following command to train the maddpg o to
