Doc improved
This commit is contained in:
12
README.md
12
README.md
@@ -1708,14 +1708,15 @@ Users can profit of running multiple **DRAMSys + gem5 simulations**
|
||||
automatically with
|
||||
[gem5ilva](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh) for **gem5
|
||||
syscall emulation (SE) mode** and
|
||||
[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh) for
|
||||
[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva_fs.sh) for
|
||||
**gem5 full system (FS) mode**.
|
||||
|
||||
Normally you will have to push your changes before running the scripts. This
|
||||
approach makes it easier to track back what exactly was tested by the scripts.
|
||||
|
||||
In the scripts there are variables to tell **git** where to get the source
|
||||
code from, user name, **branch**, etc. The variable are:
|
||||
code from (the repository URL), user name to be used by git (from your git
|
||||
account), **branch** (your working branch), etc. The variable are:
|
||||
|
||||
```bash
|
||||
# Git info.
|
||||
@@ -1725,6 +1726,9 @@ git_url="git.eit.uni-kl.de:ems/astdm/dram.sys.git"
|
||||
git_url_https="git.eit.uni-kl.de/ems/astdm/dram.sys.git"
|
||||
```
|
||||
|
||||
Open the script in QtCreator or another text editor of your choice and set the
|
||||
variables with values that fit your needs.
|
||||
|
||||
Nevertheless, for some cases, you may want to have gem5 files out of the main
|
||||
repository (usually because they are too big to be added to the repository).
|
||||
|
||||
@@ -1736,6 +1740,10 @@ This will allow you to use a gem5 **config.ini** file external to the
|
||||
repository. Note, however, that in this case it is up to you to keep track of
|
||||
your simulation files.
|
||||
|
||||
**Hint:**
|
||||
[gem5.TnT](https://github.com/tukl-msd/gem5.TnT) provides convenience scripts
|
||||
to create gem5 disk images with benchmarking programs embedded.
|
||||
|
||||
### Notes for [Elwetritsch](https://elwe.rhrk.uni-kl.de/) Users
|
||||
|
||||
Firstly, take a look at [High Performance Computing at the TU
|
||||
|
||||
Reference in New Issue
Block a user