Hello,
The OpenCSD manual HOWTO.md mentions the ~/.debug directory with the following comment:
Perf is expecting files related to the trace capture (perf.data) to be located under ~/.debug [3]. (...) [3]: Get in touch with us if you know a way to change this.
Source: https://github.com/Linaro/OpenCSD/blob/master/HOWTO.md
I've just discovered how to control this, so I'm sharing. I'm not sure about your pull request policy on OpenCSD contribution, so I decided to use mailing list for that.
This setting can be adjusted with the `perf config` command as follows:
root@zynq:~# ls -l my_buildid ls: cannot access 'my_buildid': No such file or directory
root@zynq:~# perf config --system buildid.dir=/root/my_buildid
root@zynq:~# perf record -e cs_etm/@fe950000.etf2/u --per-thread ./testprogram Couldn't synthesize bpf events. ^C[ perf record: Woken up 4 times to write data ] Warning: AUX data lost 3 times out of 3!
[ perf record: Captured and wrote 0.029 MB perf.data ]
root@zynq:~# ls -l my_buildid total 16 drwxr-xr-x 3 root root 4096 Apr 18 16:06 '[kernel.kallsyms]' drwxr-xr-x 3 root root 4096 Apr 18 16:06 '[vdso]' drwxr-xr-x 3 root root 4096 Apr 18 16:06 lib drwxr-xr-x 3 root root 4096 Apr 18 16:06 root
More examples on perf-config: http://man7.org/linux/man-pages/man1/perf-config.1.html
Best regards, Wojciech
Hi Wojciech,
On Thu, 18 Apr 2019 at 08:17, Wojciech Żmuda wzmuda@n7space.com wrote:
Hello,
The OpenCSD manual HOWTO.md mentions the ~/.debug directory with the following comment:
Perf is expecting files related to the trace capture (perf.data) to be located under ~/.debug [3]. (...) [3]: Get in touch with us if you know a way to change this.
Source: https://github.com/Linaro/OpenCSD/blob/master/HOWTO.md
I've just discovered how to control this, so I'm sharing. I'm not sure about your pull request policy on OpenCSD contribution, so I decided to use mailing list for that.
Very good - thanks for taking the time to share this information. We are always happy to receive patches - you can either use the github interface or generate a patch "kernel style" and send it to the list.
Regards, Mathieu
This setting can be adjusted with the `perf config` command as follows:
root@zynq:~# ls -l my_buildid ls: cannot access 'my_buildid': No such file or directory
root@zynq:~# perf config --system buildid.dir=/root/my_buildid
root@zynq:~# perf record -e cs_etm/@fe950000.etf2/u --per-thread ./testprogram Couldn't synthesize bpf events. ^C[ perf record: Woken up 4 times to write data ] Warning: AUX data lost 3 times out of 3!
[ perf record: Captured and wrote 0.029 MB perf.data ]
root@zynq:~# ls -l my_buildid total 16 drwxr-xr-x 3 root root 4096 Apr 18 16:06 '[kernel.kallsyms]' drwxr-xr-x 3 root root 4096 Apr 18 16:06 '[vdso]' drwxr-xr-x 3 root root 4096 Apr 18 16:06 lib drwxr-xr-x 3 root root 4096 Apr 18 16:06 root
More examples on perf-config: http://man7.org/linux/man-pages/man1/perf-config.1.html
Best regards, Wojciech _______________________________________________ CoreSight mailing list CoreSight@lists.linaro.org https://lists.linaro.org/mailman/listinfo/coresight
-
Mathieu Poirier -
Wojciech Żmuda