[lkml]   [2000]   [Sep]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] 2.4.0 i386 watchpoint problems
> 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 <>
Etnus, LLC. +44 117 9071438

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.131 / U:23.788 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site