- Added and updated documentation for gem5

- Added gem5 configuration used for profiling

git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@2027 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
This commit is contained in:
friemel
2013-01-30 23:59:32 +00:00
parent 7588834f41
commit db35166d67
4 changed files with 228 additions and 3 deletions

View File

@ -213,15 +213,18 @@ Building gem5:
Fail* configuration:
------------------------------------------------------------
- BUILD_GEM5 ON
- BUILD_ARM ON
- all configuration options specific for other simulators OFF
- COMPILER: gcc (not ag++)
- Release or Debug choice must match gem5 in the following
For the first time:
------------------------------------------------------------
1. Change to the gem5 simulator directory (expects to be in ${FAIL_DIR}):
$ cd simulators/gem5
2. Get the gem5 sourcecode from the stable repository (Mercurial needed)
$ hg clone http://repo.gem5.org/gem5-stable ./
2. Build gem5 using the commands below until it fails finding the fail-libs
3. Build fail
4. Select an experiment (see below)
5. Build gem5 again. THe fail-libs should be found now.
Optimized build:
------------------------------------------------------------
@ -234,3 +237,11 @@ Debug build:
$ cd ../simulator/gem5
$ scons EXTRAS=../../src/core/sal/gem5 build/ARM/gem5.debug
(add -jN for a parallel build)
Selecting an experiment:
------------------------------------------------------------
1. Edit ../src/core/sal/gem5/SConscript
In line starting with (gStaticLibs = ...) change -lfail-arch-test to
-lfail-EXPERIMENTNAME

View File

@ -175,3 +175,13 @@ Some useful things to note:
overflow the server with requests. You may need to bundle parameters for
more than one experiment if a single experiment only takes a few hundred
milliseconds. (See existing experiments for examples.)
=========================================================================================
Steps to run an experiment with gem5:
=========================================================================================
1. Create a directory which will be used as gem5 system directory (which
will contain the guest system and boot image). Further called $SYSTEM.
2. Create two directories $SYSTEM/binaries and $SYSTEM/disks.
3. Put guestsystem kernel to $SYSTEM/binaries and boot image to $SYSTEM/disks
4. Run gem5 with:
$ M5_PATH=$SYSTEM build/ARM/gem5.debug configs/example/fs.py --bare-metal --kernel kernelname