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

rungdb-user: failed attempt with rungdb factor

Browse Source
This commit is contained in:
Ciro Santilli
2018-08-31 17:05:34 +01:00
parent de682e80c7
commit 8c16820365
5 changed files with 124 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -8998,13 +8998,13 @@ time \
and this line is also saved to a file for convenience:
....
cat "$(./getvar -a arm run_dir)/cmd.sh"
cat "$(./getvar -a arm run_cmd_file)"
....
or for gem5:
....
cat "$(./getvar -a arm -g run_dir)/cmd.sh"
cat "$(./getvar -a arm -g run_cmd_file)"
....
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>/cmd.sh`: full CLI used to run QEMU. See: <<report-upstream-bugs>>
*** `out/<arch>/qemu/<run-id>/run.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>/cmd.sh`: full CLI used to run gem5. See: <<report-upstream-bugs>>
**** `out/<arch>/gem5/<run-id>/run.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.