Hi Ayaz,
I cloned the repository from https://github.com/gem5/gem5.git
built with command python3 `which scons` build/X86/gem5.opt -j13
and got warnings
> Warning: Deprecated namespaces are not supported by this compiler.
> Please make sure to check the mailing list for deprecation
> ann
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
Hi Haseung,
I am not sure if I have fully understood the question, but I will try to
answer based on my understanding (please let me know if I misunderstood).
SE mode, on a TLB miss, makes use of the gem5 managed page table for the
simulated process instead of modeling a page table walk and I gues
Hi Le Minh Son,
In my opinion, if you are well aware of the ISA specs and know how your new
instruction will fit in with the existing instructions, you might add a
real instruction. Otherwise, adding a pseudo instruction might be a better
option. Following are some of the references that you might
Hi Brian,
Can you share the script/configuration that ran into the problem with the
stable branch? I did a quick test with the traffic generator (with two
different mem devices) and things seem to work ok on my end.
Thanks,
-Ayaz
On Sat, Mar 11, 2023 at 9:33 AM Brian Chan via gem5-users <
gem5-u
Dear gem5-ers -
I wanted to set up to use NVM only, so I tried this on the command line:
--nvm-type=NVM_2400_1x64
This had no effect. Digging into configs/common/MemConfig.py was not directly
enlightening. However, it seems that Options.py sets mem-type to a particular
DRAM by default. Doi
