RFC hw-breakpoint interfaces for BookE - ver I
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 1 patch 0 repliesNew
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC Patch 0/1] [hw-bkpt BookE] hw-breakpoint interfaces for BookE - ver I
Hi All,
Please find a patch that implements hardware-breakpoint interfaces for
BookE processors. The patches are under continuous development and are sent to receive early comments. For the moment, they are (only) compile tested (with ppc64e_defconfig), further testing will accompany the ongoing development.
A few notes about the patchset, as below:
- The patch is designed with reference to BookIII-E type processors specification (having two DAC/DVC registers).
- Instruction breakpoint requests are not implemented through the generic breakpoint interfaces. Such requests are still possible for user-space through ptrace.
- Breakpoint exceptions are designed to 'trigger-after-execute', although the processors raise the exception before instruction execution. To achieve this, the causative insruction is single-stepped over and the breakpoint handler is invoked in the ICMP exception handler.
- The patches are dependant on the recent submissions (not yet integrated into mainline) that bring support for hw-breakpoint weight (patchset from Frederic Weisbecker LKML ref:[email protected]) and PPC64 hw-breakpoint support (linuxppc-dev ref:[email protected]).
Here are a few items identified to work upon in the successive versions. TO DO
------
- Modify ptrace requests to use the generic hw-breakpoint interfaces (PTRACE_<GET><SET>_DEBUGREG, PTRACE_SETHWDEBUG)
- Explore intergration of BookE and BookS code intergration (hw_breakpoint.c and hw_breakpoint_booke.c)
- Code clean-up and reduction.
Kindly let me know about comments/suggestions, if any.
Thank You,
K.Prasad