Re: [patch 5/8] Immediate Values - kprobe header fix

2007-07-14 Thread Mathieu Desnoyers
Should be dropped, following Christoph's advice. * Mathieu Desnoyers ([EMAIL PROTECTED]) wrote: > Since the immediate values depend on the same int3 handler as kprobes > implements > for i386, we have to get architecture specific defines available for the > kprobes > trap handler (especially res

Re: [patch 5/8] Immediate Values - kprobe header fix

2007-07-14 Thread Christoph Hellwig
On Fri, Jul 13, 2007 at 09:24:44PM -0400, Mathieu Desnoyers wrote: > Since the immediate values depend on the same int3 handler as kprobes > implements > for i386, we have to get architecture specific defines available for the > kprobes > trap handler (especially restore_interrupts()) wven when C

[patch 5/8] Immediate Values - kprobe header fix

2007-07-13 Thread Mathieu Desnoyers
Since the immediate values depend on the same int3 handler as kprobes implements for i386, we have to get architecture specific defines available for the kprobes trap handler (especially restore_interrupts()) wven when CONFIG_KPROBES is not selected. That kind of ifdef around a whole header does n