mirror of
https://github.com/cirosantilli/linux-kernel-module-cheat.git
synced 2026-01-23 02:05:57 +01:00
gem5-src: document saner defaults
This commit is contained in:
1
.gitignore
vendored
1
.gitignore
vendored
@@ -17,6 +17,7 @@ gitignore*
|
|||||||
__pycache__
|
__pycache__
|
||||||
|
|
||||||
# Accidents.
|
# Accidents.
|
||||||
|
/core
|
||||||
/m5out
|
/m5out
|
||||||
*.o
|
*.o
|
||||||
*.out
|
*.out
|
||||||
|
|||||||
14
README.adoc
14
README.adoc
@@ -10679,22 +10679,18 @@ Next, when you want to build with this repository, use the `--gem5-src` argument
|
|||||||
....
|
....
|
||||||
cd linux-kernel-module-cheat
|
cd linux-kernel-module-cheat
|
||||||
./build-gem5 \
|
./build-gem5 \
|
||||||
--gem5-build-id p/lkmc/master \
|
--gem5-build-id p/master \
|
||||||
--gem5-src "$gem5_internal" \
|
--gem5-src "$gem5_internal" \
|
||||||
--gem5-worktree p/lkmc/master \
|
--gem5-worktree p/master \
|
||||||
;
|
;
|
||||||
./run-gem5
|
./run-gem5
|
||||||
--gem5-build-id p/lkmc/master \
|
--gem5-build-id p/master \
|
||||||
--gem5-src "$gem5_internal" \
|
--gem5-src "$gem5_internal" \
|
||||||
--gem5-worktree p/lkmc/master \
|
--gem5-worktree p/master \
|
||||||
;
|
;
|
||||||
....
|
....
|
||||||
|
|
||||||
`p/lkmc/` is not mandatory but it provides a sane default:
|
`p` stands for Private, and is not mandatory, but it is a sane default that will remind you at all times that you are dealing with private code instead of public.
|
||||||
|
|
||||||
* `p` stands for `private`, and will separate the private from public builds
|
|
||||||
* `lkmc` is added to prevent name conflicts with other work-trees of the private repository
|
|
||||||
* `master`, finally, reflects that the worktree is at the `master` state of private repository
|
|
||||||
|
|
||||||
This setup only creates gitignored worktrees of the private repository inside this repository, which is pretty safe, while still allowing fully use our infrastructure as usual.
|
This setup only creates gitignored worktrees of the private repository inside this repository, which is pretty safe, while still allowing fully use our infrastructure as usual.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user