Hi Eliot, Yes, that's right. The reason is that the parameter for memory interface in MemCtrl.py ( https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/src/mem/MemCtrl.py) is called dram even though it can be an NVM interface. I think this should be fixed to remove the confusion, but the change can also break existing gem5 run scripts. In any case, I will try to push a change to make it less confusing.
-Ayaz On Sun, Mar 19, 2023 at 3:43 AM Eliot Moss <m...@cs.umass.edu> wrote: > On 3/18/2023 10:40 PM, Ayaz Akram via gem5-users wrote: > > Hi Eliot, > > > > MemCtrl() memory controller in gem5 can control a single DRAM interface > or a single NVM interface at > > a time. I think one way to verify that things are set-up correctly is to > confirm this from the > > "m5out/config.ini". If config.ini seems to be using 'MemCtrl' type for > the memory controller and the > > memory interface connected to the controller is of the type > 'NVMInterface', I think that should > > confirm that you are simulating an NVM device. > > Thanks, Ayaz! Yes, that's what I get. It seems odd that the component > gets named blah-blah.dram, but it clearly says NVMInterface, so that's ok. > > I appreciate the confirmation. > > Eliot >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
