hi,I started implementing GDB process record and replay with ARM CoreSight as described in the rfc published early this year. Current implementation of coresight tracing in Perf is based on the sysfs interface, by accessing /sys/bus/event_source/devices/cs_etm ... file. GDB implementation of bts and ipt is based on the syscall "sys_perf_event_open".it would be nice to use the similar mechanism for realizing similar functionalities. therefore I would like to know if linux kernel (with coresight deivers) is exposing coresight drivers through the syscall sys_perf_event_open and if this is the case how shall I configure the perf_event_attr to use it.
thanks Zied Guermazi
# Progress #
o Upstream GDB
* ARM sim build failure with -fno-common
- Sent a patch to gdb-patches. Going through rounds of reviews.
* Patch reviewing and answering community questions.
o GDB
* GNU-644 - [GDB, AArch64] gdb.base/step-over-syscalls.exp failures
- Spent some more time with this in the hopes of understanding the
various failure modes. Still not clear if the kernel is doing the right
thing. It may be hard to adjust things on GDB's side, but i have a
couple patches solving some of the problems.
o Misc
* Updated personal information in the HR system.
# Plan #
o Upstream GDB
* Get approval for the fix to -fno-common build issues with ARM sim.
o GDB
* GNU-644 - [GDB, AArch64] gdb.base/step-over-syscalls.exp failures
- Engage with kernel folks for better understanding of signal
delivery scheme. Polish current fixes and submit for review.
o LLVM:
* Machine Outliner:
- Disabled asm statements.
- Added Helium LD/ST instructions support
- Adding testcases
o Misc
* Various meetings and discussions.