3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

gem5: explain -N a bit better

Browse Source
This commit is contained in:
Ciro Santilli
2018-08-16 18:11:50 +01:00
parent 433e60f876
commit b57baebe87
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.adoc
View File

@@ -8733,7 +8733,7 @@ This becomes inevitable when you want to launch <<gem5-simultaneous-runs-with-bu
===== gem5 simultaneous runs with build variants
In order to checkout multiple gem5 builds and run them simultaneously, you also need to use the `-N`:
In order to checkout multiple gem5 builds and run them simultaneously, you also need to use the `-N` flag:
....
./build -g
@@ -8744,6 +8744,8 @@ git -C gem5/gem5 checkout -
./run -g -M some-branch -N some-branch -n 1 &>/dev/null &
....
When `-N` is not given, the default source tree under `gem5/gem5` is used.
The `-N <woktree-id>` determines the location of the gem5 tree to be used for both:
* the input C files of the build at build time
@@ -8751,8 +8753,6 @@ The `-N <woktree-id>` determines the location of the gem5 tree to be used for bo
The difference between `-M` and `-N` is that `-M` specifies the gem5 build output directory, while `-N` specifies the source input directory.
When `-N` is not given, source tree under `gem5/gem5` is used.
If `-N <worktree-id>` is given, the directory used is `data/gem5/<worktree-id>`, and:
* if that directory does not exist, create a `git worktree` at a branch `wt/<worktree-id>` on current commit of `gem5/gem5` there.
@@ -8760,6 +8760,13 @@ If `-N <worktree-id>` is given, the directory used is `data/gem5/<worktree-id>`,
The `wt/` branch name prefix stands for `WorkTree`, and is done to allow us to checkout to a test `some-branch` branch under `gem5/gem5` and still use `-N some-branch`, without conflict for the worktree branch, which can only be checked out once.
* otherwise, leave that worktree untouched, without updating it
Therefore, future builds for `worktree-id` will not automatically modify the revision of the worktree, and to do that you must manually check it out:
....
git -C data/gem5/some-branch checkout some-branch-v2
./build -g -M some-branch -N some-branch
....
`-N` is only required if you have multiple gem5 checkouts, e.g. it would not be required for multiple builds of the same tree, e.g. a <<gem5-debug-build>> and a non-debug one.
===== gem5 debug build