Hey Yogeshwaran,

Since the gem5-20.1 release, it now supports DRAMSim3 integration so there
is no need for you to follow the instructions there. There is a readme file
in ext/dramsim3 that you can follow and build gem5 with DRAMSim3, also,
class DRAMSim3 inherits from AbstractMemory which will allow you to swap
any memory with DRAMSim3 models. To change the model you want to use in
DRAMSim3 you can just change the path to the .ini file you are  using by
changing param configFile.

Best Regards

On Tue, Nov 24, 2020 at 5:30 AM Yogeshwaran L via gem5-users <
[email protected]> wrote:

> Dear gem5 community,
>
> I am trying to integrate DRAMsim3 with gem5, and I was able to
> successfully build gem5 with DRAmsim3, following the instructions from
> https://github.com/umd-memsys/gem5/tree/dramsim3/ext/dramsim3.
>
> However, in the last step it is mentioned "Use --mem-type=dramsim3 and set
> the device and system configuration". But when I looked at the
> configuration script (simple.py) in part1 of learning_gem5 directory, there
> are many fields to be configured for memory.
>
> Can anyone point me to resources or offer any advice on how to use a
> different memory system(like DRAMsim3) with gem5 and configure the
> parameters in configuration script. Is it as straightforward as configuring
> the config script or should I do additional modifications?
>
> Thank you,
> Yogeshwaran
> _______________________________________________
> gem5-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s



-- 
Mahyar Samani (he/him/his)
Electrical and Computer Engineering Department
Research Assistant at *DArchR <https://arch.cs.ucdavis.edu/> (*2235 Kemper
Hall)
Secretary
ECE-GSA
Vice President
Iranian Student Association at UC Davis
University of California, Davis
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to