From 4085dfd7b3f94e25f17b7a317ff407956fd440d2 Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Sun, 12 Aug 2018 21:13:53 +0100 Subject: [PATCH] readme: fix some directories 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. --- README.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index 9bfb362..5e02c5a 100644 --- a/README.adoc +++ b/README.adoc @@ -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 <> 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: