Hardware Breakpoint Interfaces - v5
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 11 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 11 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Patch 00/11] Hardware Breakpoint Interfaces - v5
Hi Ingo,
Please find the new set of patches that implement Hardware
breakpoint interfaces for kernel- and user-space, an ftrace plugin using these interfaces to trace memory accesses over kernel symbols and a demonstrative example.
While a previous version of these patches was posted
here: http://lkml.org/lkml/2009/3/7/23 and generated substantial amount of discussions over LKML, a summary of proposed changes to the patchset was posted
here: http://lkml.org/lkml/2009/3/13/381.
In short, the infrastructure has been changed to provide interfaces to use Hardware Breakpoint (or Watchpoint) registers on a first-come first-serve basis (without over-committing resources). The serviced-requests are maintained in an array of pointers to the register's datastructure. Requests from kernel-space will be serviced in decreasing order of register numbers (starting from HB_NUM - 1).
The ksym_tracer ftrace plugin now also contains a startup self-test and support for showing aggregate counters (through ftrace's histogram infrastructure).
Kindly let me know if the new patchset addresses the concerns of the community and is deemed fit for inclusion in -tip tree. The patchset is based on commit 62f84ea922bd60803e446153ea99ce5d7245d6f9 of -tip tree.
Thanks,
K.Prasad