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

readme: fix some directories

Browse Source 
TODO: maybe I should automate all that stuff with some magic helper
that exposes internal paths, otherwise the docs break on every refactor
and it is very hard to fix them up.
This commit is contained in:
Ciro Santilli
2018-08-12 21:13:53 +01:00
parent 4e648479f2
commit 4085dfd7b3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@@ -1154,7 +1154,7 @@ You can also add a prefix to the build ID before a period:
which then uses the output directory:
....
less out/aarch64/gem5/default/some-experiment.1/m5out
less out/aarch64/gem5/some-experiment.1/m5out
....
and makes it easier to remember afterwards which directory contains what.
@@ -7288,7 +7288,7 @@ Trace the source lines just like <<trace-source-lines,for QEMU>> with:
....
./trace-boot -a aarch64 -g && ./trace2line -a aarch64 -g
less ./out/aarch64/gem5/trace-lines.txt
less ./out/aarch64/gem5/0/trace-lines.txt
....
TODO: 7452d399290c9c1fc6366cdad129ef442f323564 `./trace2line` this is too slow and takes hours. QEMU's processing of 170k events takes 7 seconds. gem5's processing is analogous, but there are 140M events, so it should take 7000 seconds ~ 2 hours which seems consistent with what I observe, so maybe there is no way to speed this up... The workaround is to just use gem5's `ExecSymbol` to get function granularity, and then GDB individually if line detail is needed?
@@ -7564,7 +7564,7 @@ So we take a performance measurement approach instead:
....
./gem5-bench-cache -a aarch64
cat out/aarch64/gem5/bench-cache.txt
cat out/aarch64/gem5/0/bench-cache.txt
....
which gives: