Hardware Breakpoint interfaces
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 11 patches 7 repliesIn review
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
Hi Alan,
I am sending you the patches with the changes mentioned in the
Changelog below. Please read the patches in conjunction with my replies sent to your previous comments.
Let me know your thoughts on this.
Changelog
-----------
- Introduce (un)register_user_hw_breakpoint() which would take two parameters - pointer to 'struct task_struct' and 'struct hw_breakpoint'.
- Change the return value behaviour in ptrace(). Return '0' for write in DR0 - DR3 (with the exception being when the registered address is not in user-space), while restricting error returns for write in DR7. Move memory (de)allocation behaviour for 'struct hw_breakpoint' to ptrace related code and flush_thread_hw_breakpoint() from unregister_user_hw_breakpoint() code.
- Addition of arch_flush_thread_hw_breakpoint() to zero-out thread->debugreg[n] registers.
- Consolidate arch-specific kernel/thread update routines into arch_update_kernel_hw_breakpoints() and arch_update_user_hw_breakpoint() routines.
- Re-arrange the patchset to enable compilation after application of every patch in the patchset.
- hw_breakpoint_handler() modified to:
- Unconditionally invoke (*trigger) function call
- Return NOTIFY_DONE only when other bits in DR6 are set or when breakpoint originates due to an address in user-space
- Do an early return if trap bits are not set and we have entered the handler because of BT, BS or BD bits in dr6 being set.
- samples/hw_breakpoint/data_breakpoint.c modified to accept module parameters
The patchset is based on commit f0e36dc28173b65df2216dfae7109645d97a1bd9 of -tip tree.
Thanks,
K.Prasad