Re: [patch 3/3] Text Edit Lock - kprobes i386

2007-07-05 Thread Mathieu Desnoyers
This suggestion looks more like a workaround to get rid of a bigger issue. If we do that, we have to use CONFIG_* exclusivity for either (ro-data protection) or (paravirt, kprobes, immediate values). One big advantage of my patch is that we can remove weird exclusivity cases involving paravirt a

Re: [patch 3/3] Text Edit Lock - kprobes i386

2007-07-04 Thread S. P. Prasanna
On Tue, Jul 03, 2007 at 12:38:22PM -0400, Mathieu Desnoyers wrote: > Kprobes can use the text edit lock to insure mutual exclusion when edition the > code and make sure the pages are writable. Linus suggested for splitting ro-data and ro-text; And allow ro-text only if kprobes is not configured. P

[patch 3/3] Text Edit Lock - kprobes i386

2007-07-03 Thread Mathieu Desnoyers
Kprobes can use the text edit lock to insure mutual exclusion when edition the code and make sure the pages are writable. Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] --- arch/i386/kernel/kprobes.c |

[patch 3/3] Text Edit Lock - kprobes i386

2007-06-18 Thread Mathieu Desnoyers
Kprobes can use the text edit lock to insure mutual exclusion when edition the code and make sure the pages are writable. Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]> --- arch/i386/kernel/kprobes.c |4 1 file changed, 4 insertions(+) Index: linux-2.6-lttng/arch/i386/kernel/kprob