[RFC,PATCH 07/14] ptrace: x86: change syscall_trace_leave() to rely on tracehook when stepping

2009-11-24 Thread Oleg Nesterov
(already in mm: ptrace-x86-change-syscall_trace_leave-to-rely-on-tracehook-when-stepping.patch) Suggested by Roland. Unlike powepc, x86 always calls tracehook_report_syscall_exit(step) with step = 0, and sends the trap by hand. This results in unnecessary SIGTRAP when PTRACE_SINGLESTEP follows

[PATCH 7] ptrace: x86: change syscall_trace_leave() to rely on tracehook when stepping

2009-11-22 Thread Oleg Nesterov
(already in mm: ptrace-x86-change-syscall_trace_leave-to-rely-on-tracehook-when-stepping.patch) Suggested by Roland. Unlike powepc, x86 always calls tracehook_report_syscall_exit(step) with step = 0, and sends the trap by hand. This results in unnecessary SIGTRAP when PTRACE_SINGLESTEP follows

tracehook is in!

2008-07-28 Thread Roland McGrath
We had a pleasant surprise over the weekend. The tracehook branch was merged in upstream! As of 2.6.26-git18, the generic tracehook patches plus the powerpc and sparc64 arch work are all in. The x86-tracehook branch is in the hands of the x86 arch maintainers and I expect it will get pushed up

Re: tracehook interface style

2008-01-02 Thread Wenji Huang
as the pointers passed (and now unused) in those calls you mentioned. (Because these are actually inlines, any unused parameters compile away completely. If any core code calling tracehook functions were ever to change so that one of these items were no longer already on hand, then we would change the tracehook