On Mon, 12 Mar 2018 23:40:55 +0900
Masami Hiramatsu <mhira...@kernel.org> wrote:
> Since we decided to remove jprobe from kernel last year,
> its APIs are disabled and we worked on moving in-kernel
> jprobe users to kprobes or trace-events. And now no jprobe
> users are here anymore.
> This series removes jprobe implementation from x86 and
> generic code. I would like to send other series for each
> arch. After all those patches are merged, I will remove
> jprobes APIs and data structures, since changing those
> definitions will break build on other archs.
> Here is the series of patches to show how to do that.
> I've dropped arch-independent header changes from this
> version and merged kprobe-user code changes into the
> last patch since that changed the kprobes expected
> behavior when the kprobes modifies execution path.
> (no need to enable preempt anymore)
> - Remove jprobe functions (register/unregister,
> setjump/longjump) from generic/arch-dependent code.
> - Remove break_handler related code.
> - Do not disable preemption on exception handler
> As I said above, the last patch [5/5] will change the
> expected behavior on x86. Other archs also have to change
> it. But anyway, currently such execution-path modifying
> users in tree are very limited and only works on x86.
> So we can safely modify it.
Ah, I forgot I had sent this in March...
Basically, this is same thing what I sent last week, and this is more
aggressively removing all the jprobes related code including
break_handler. I would like to merge both series and start sending
new series, including removing jprobe test code too.
Masami Hiramatsu <mhira...@kernel.org>