这个项目是基于https://github.com/kuczmmar/Running-ahead-of-memory-latency的修改版本。
增加了/gem5/configs/runahead/Rewrite.py，这个文件是/gem5/configs/runahead/o3_2level.py的复制衍生版本，主要增加了对“--MaxInsts”命令的识别以指定最大指令执行数。
修改了/gem5/run.sh 主要增加了对spec2006的一些benchmark的路径（这些bench不在本项目中，使用时请修改为你本地的bench路径），同时调整了gem5运行脚本，改变为ReWrite.py，增加对最大指令数的指定(这个参数可以在run.sh中修改)。
在目前的测试中，原作者实现的Pre cpu 存在潜在的问题。
Runahead and Precise Runahead Execution implementation using system simulator gem5
This is the repository used for my final year projectduring my Computer Science degree at the University of Cambridge. The project is fully described in my dissertation --- ''Running ahead of memory latency - processor runahead'', which can be found in this repository. My implementations are based on the papers that proposed runahead and PRE.
Following the online gem5 tutorial, the recommended way tp install all dependencies on Ubuntu is to run the following command:
sudo apt install build-essential git m4 scons zlib1g zlib1g-dev libprotobuf-dev protobuf-compiler libprotoc-dev libgoogle-perftools-dev python-dev pythonClone the repository.
The best place to start learning gem5 is the online tutorial.
To run my simulation setup enter the gem5 and in script run.sh ammend line number 15, this is responsible for compiling gem5. On a computer with 8 cores the recommended way to compile is:
python3 `which scons` build/X86/gem5.opt -j9Alternatively, one can specify the exact path to scons directory. Given more cores, you can increase the parallelisation parameter e.g. on a 32 core machine:
python3 ./bin/scons build/X86/gem5.opt -j33To compile gem5 and run the test script simply use:
./gem5/run.sh -cTo only run the tests:
./gem5/run.sh| Top | Subfolders | Description | |
|---|---|---|---|
| gem5/ | Source code of the gem5 simulator tool version 21.1.0.2. | ||
| src/cpu/ | o3/ | The baseline CPU implementation. | |
| ra/ | The runahead CPU that extends O3CPU. | ||
| pre/ | The PRE CPU that extends O3CPU. | ||
| src/mem/ | The memory system, contains caches and MSHRs. | ||
| src/kern/ | Implementation of system-call interfaces. | ||
| configs/ | Python scripts configuring architecture features. | ||
| m5out/ | Simulation statistics (used by McPAT). | ||
| stats/ | Scripts for parsing and displaying chosen statistics. | ||
| build/ | The build directory contains gem5's binary files. | ||
| benchmarks/ | cbench/ | {Banchmarks based on standard type files e.g.~txt, png, mp3. | |
| cgo2017/ | Memory-latency bound benchmarks. | ||
| parsing_data/ | mcpat/ | Source code of the McPAT power consumption tool (https://github.com/HewlettPackard/mcpat). | |
| Gem5McPatParser | Script converting gem5 statistics to a format used by McPAT based on (https://github.com/saitiku/Gem5McPatParser). | ||
| parse.py | Script that runs parsing and McPAT, saves the output. | ||
| mcpat_in/ | Output of Gem5McPatParser and input to McPAT. | ||
| mcpat_out/ | This is where energy output from McPAT after running the parse.py script. | ||
| plotting_stats/ | Parsing and plotting statistics and McPAT output. |
Copyright (c) 2022, Marta Walentynowicz All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
-
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.