configs,ext,stdlib: Update DRAMSys integration (#525)

Recent breaking changes in the DRAMSys API require user code to be
updated. These updates have been applied to the gem5 integration.

Furthermore, as DRAMSys started to use CMake dependency management,
it is no longer sensible to maintain two separate build systems for
DRAMSys. The use of the DRAMSys integration in gem5 will therefore
from now on require that CMake is installed on the target machine.

Additionally, support for snapshots have been implemented into DRAMSys
and coupled with gem5's checkpointing API.
This commit is contained in:
Derek Christ
2023-11-14 17:05:11 +01:00
committed by GitHub
parent 99553fdbee
commit e95cab429f
11 changed files with 330 additions and 131 deletions

View File

@@ -1,11 +1,13 @@
Follow these steps to get DRAMSys as part of gem5
Follow these steps to build DRAMSys as part of gem5
1. Go to ext/dramsys (this directory)
2. Clone DRAMSys: 'git clone https://github.com/tukl-msd/DRAMSys DRAMSys'
3. Change directory to DRAMSys: 'cd DRAMSys'
4. Checkout the correct commit: 'git checkout -b gem5 09f6dcbb91351e6ee7cadfc7bc8b29d97625db8f'
5. Recursively obtain the submodules: 'git submodule update --init --recursive'
2. Clone DRAMSys: 'git clone https://github.com/tukl-msd/DRAMSys --branch v5.0 --depth 1 DRAMSys'
The latest verified working version is v5.0, but later versions might work too.
gem5 will automatically pick up DRAMSys as an external module when it is rebuilt.
If you wish to run a simulation using the gem5 processor cores, make sure to enable the storage mode in DRAMSys.
This is done by setting the value of the "StoreMode" key to "Store" in the base configuration file.
Those configuration file can be found in 'DRAMSys/library/resources/configs/simulator'.
Currently, DRAMSys is only supported in conjunction with a cache. Running DRAMSys in Release mode without caches will silently fail!