Hi Tomasz,
On Thu, Aug 16, 2018 at 04:04:46PM +0200, Tomasz Nowicki wrote:
[...]
Now I am trying to see exactly the path a processor took through the code according to these instructions: https://github.com/Linaro/OpenCSD/blob/master/HOWTO.md#trace-decoding-with-p... However, on perf-opencsd 'perf-opencsd-v4.16' branch there is no 'cs-trace-disasm.py' script. Are you planning to add this script to mainline kernel or this was just for development purpose?
That script was provided to show what can be done with the results and was never intended to be used by a broad audience. At one point it became too difficult to maintain it and it was dropped from the patchset. You can still find it on tag "perf-opencsd-v4.15" but you'll have to make modifications so that it can work again.
OK, I will try to port it on v4.16.
Leo Yan (who is on this list) was working on upstreaming a better version of the script. That was put on hold while I am trying to finish the support of CPU-wide trace scenarios.
Hi Leo, regarding your script, do you have any working version? If yes, and you willing to share, I can give it a try on my machine.
Yes, my pleasure. Please note on the mainline kernel there have a dependent patch series for tracing packet handling fixes[1], you need firstly apply the patches firstly. Then you could refer the enclosed three patches for CoreSight trace disassembler with python script.
Thanks, Leo Yan