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

run logging works

Browse Source
This commit is contained in:
Ciro Santilli
2018-08-30 09:05:37 +01:00
parent 094b6c4275
commit ddfb34cdd4
4 changed files with 56 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.adoc
View File

@@ -8146,7 +8146,7 @@ printf 'echo "second benchmark";m5 exit' > data/readfile
./run -a aarch64 -g -l 1
....
Since this is such a common setup, we provide helper for it at: link:rootfs_overlay/gem5.sh[rootfs_overlay/gem5.sh].
Since this is such a common setup, we provide helper for it at: link:rootfs_overlay/gem5.sh[rootfs_overlay/gem5.sh]. This script is analogous to gem5's in-tree link:https://github.com/gem5/gem5/blob/2b4b94d0556c2d03172ebff63f7fc502c3c26ff8/configs/boot/hack_back_ckpt.rcS[hack_back_ckpt.rcS], but with less noise.
Other loophole possibilities include:
@@ -8998,13 +8998,13 @@ time \
and this line is also saved to a file for convenience:
....
cat "$(./getvar -a arm run_dir)/run.sh"
cat "$(./getvar -a arm run_dir)/cmd.sh"
....
or for gem5:
....
cat "$(./getvar -a arm -g run_dir)/run.sh"
cat "$(./getvar -a arm -g run_dir)/cmd.sh"
....
Next, you will also want to give the relevant images to save them time. Zip the images with:
@@ -9422,10 +9422,10 @@ The action seems to be happening at: `hw/arm/virt.c`.
**** `out/<arch>/buildroot/build/linux-custom`: symlink to a variant, custom madness that we do on top of Buildroot: <<linux-kernel-build-variants>>
**** `out/<arch>/buildroot/build/linux-custom.<variant>`: what `linux-custom` points to
*** `out/<arch>/qemu`: QEMU runtime outputs
*** `out/<arch>/qemu/<run-id>/run.sh`: full CLI used to run QEMU. See: <<report-upstream-bugs>>
*** `out/<arch>/qemu/<run-id>/cmd.sh`: full CLI used to run QEMU. See: <<report-upstream-bugs>>
*** `out/<arch>/gem5/<run-id>/`: gem5 runtime outputs
**** `out/<arch>/gem5/<run-id>/m5out`
**** `out/<arch>/gem5/<run-id>/run.sh`: full CLI used to run gem5. See: <<report-upstream-bugs>>
**** `out/<arch>/gem5/<run-id>/cmd.sh`: full CLI used to run gem5. See: <<report-upstream-bugs>>
** `out/common`: cross arch outputs, for when we can gain a lot of time and space by sharing things that are common across different archs.
*** `out/common/dl/`: Buildroot caches downloaded source there due to `BR2_DL_DIR`
*** `out/common/gem5/`: `arm` and `aarch64` have the same build.