Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Michael Ellerman
On Tue, 2007-06-26 at 09:29 +0530, Ananth N Mavinakayanahalli wrote: > On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: > > --- > > > > It isn't obvious where kprobes patches should go, is anyone "the" > > maintainer? > > Instead I've just sent this to everyone who'd touched the

Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Ananth N Mavinakayanahalli
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: > --- > > It isn't obvious where kprobes patches should go, is anyone "the" maintainer? > Instead I've just sent this to everyone who'd touched the code lately, or > might be otherwise interested. There isn't a single maintainer

Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Ananth N Mavinakayanahalli
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: > Currently jprobe.entry is a kprobe_opcode_t *, but that's a lie. On some > platforms it doesn't point to an opcode at all, it points to a function > descriptor. > > It's really a pointer to something that the arch code can turn

[PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Michael Ellerman
Currently jprobe.entry is a kprobe_opcode_t *, but that's a lie. On some platforms it doesn't point to an opcode at all, it points to a function descriptor. It's really a pointer to something that the arch code can turn into a function entry point. And that's what actually happens, none of the

[PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Michael Ellerman
Currently jprobe.entry is a kprobe_opcode_t *, but that's a lie. On some platforms it doesn't point to an opcode at all, it points to a function descriptor. It's really a pointer to something that the arch code can turn into a function entry point. And that's what actually happens, none of the

Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Ananth N Mavinakayanahalli
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: Currently jprobe.entry is a kprobe_opcode_t *, but that's a lie. On some platforms it doesn't point to an opcode at all, it points to a function descriptor. It's really a pointer to something that the arch code can turn into a

Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Ananth N Mavinakayanahalli
On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: --- It isn't obvious where kprobes patches should go, is anyone the maintainer? Instead I've just sent this to everyone who'd touched the code lately, or might be otherwise interested. There isn't a single maintainer for the

Re: [PATCH 1/3] Make struct jprobe.entry a void *

2007-06-25 Thread Michael Ellerman
On Tue, 2007-06-26 at 09:29 +0530, Ananth N Mavinakayanahalli wrote: On Tue, Jun 26, 2007 at 11:48:50AM +1000, Michael Ellerman wrote: --- It isn't obvious where kprobes patches should go, is anyone the maintainer? Instead I've just sent this to everyone who'd touched the code lately,