[...] There is basically one single instruction trap handler that
the stap translator will generate with logic to figure out what
handler code to run [...]
The "existing kernel API" is the key issue here. How exactly does one
activate single-stepping traps on each of the interesting
architectures, and on multiple different kernel generations (RHEL)?
How does one hook into the handling system correctly (avoiding
interference to other consumers of trap data like gdb, uprobes)?
These questions need answers in order for systemtap to generate code
to implement this.
- FChE