On Mon, Jun 04, 2018 at 02:13:48PM -0600, Mathieu Poirier wrote:
On Fri, Jun 01, 2018 at 05:58:40PM +0800, Leo Yan wrote:
This commit documents CoreSight trace disassembler usage and gives example for it.
Signed-off-by: Leo Yan leo.yan@linaro.org
Documentation/trace/coresight.txt | 52 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+)
diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c..b8f2359 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -381,3 +381,55 @@ sort example is from the AutoFDO tutorial (https://gcc.gnu.org/wiki/AutoFDO/Tuto $ taskset -c 2 ./sort_autofdo Bubble sorting array of 30000 elements 5806 ms
+Tracing data disassembler +-------------------------
+'perf script' supports to use script to parse tracing packet and rely on +'objdump' for disassembled lines, this can convert tracing data to readable
Isn't better to use an arch specific objdump, something like aarch64-linux-gnu-objdump?
Yeah, will change for this. I usually test with Debian on Hikey board; I will test cross envirnment on PC and use aarch64-linux-gnu-objdump command. And will change the doc for this.
[...]
Thanks, Leo Yan