Messages in this thread |  | | Subject | Re: [PATCH] 2.4.0 i386 watchpoint problems | Date | Fri, 22 Sep 2000 10:15:29 +0100 | From | James Cownie <> |
| |
> Actually, even simpler approach: > > - always clear db7 after sending signal - don't test for pending or for > kernel mode at all at that point. > - re-load %db7 at the top of the for(;;) loop in do_signal(). > > That should mean that you will actually get a debug signal for ALL > triggers of the debug registers, except you'll only get one for kernel > mode.
This is obviously much better (getting a signal for ALL debug register triggers is a _good_ thing), but is it safe to call force_sig_info from the debug trap handler if it was entered from kernel mode ?
Since the debug trap handler can (potentially) be entered as a result of _any_ store instruction in the kernel, it's certainly not clear to me that I wouldn't be violating locking assumptions by calling force_sig_info from here...
-- Jim
James Cownie <jcownie@etnus.com> Etnus, LLC. +44 117 9071438 http://www.etnus.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |