[lkml]   [2019]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/2] Enable new kprobe event at boot
On Wed, 22 May 2019 00:39:32 +0900
Masami Hiramatsu <> wrote:

> > Perhaps we could enable kprobes at early init?
> It should be possible, I will try to find what blocks it. I guess after we
> switch early_text_poke() to text_poke(), we can use kprobes on x86. But
> for other archs, I need to investigate more.

OK, I just follow the kernel init related to kprobes

-> trace_init()
-> rcu_init_nohz()
-> perf_event_init()
-> arch_call_rest_init()
-> rest_init()
-> rcu_scheduler_starting()
-> kernel_thread(kernel_init)
-> kernel_init_freeable()
-> wait_for_completion(&kthreadd_done);
-> workqueue_init()
-> smp_init()
-> do_basic_setup()
-> do_initcalls()
-> do_initcall_level()
(in subsys-level)
-> init_kprobes()

Since optprobe uses workqueue, we can not move it before workqueue_init().
(but maybe we can disable it in early stage)
Also, since kprobes depends on rcu, I guess we can not move it before
for kretprobe, we need to get the possible cpus, we need a fix if we move
it before before smp_init().
However, there is no reason we need to run it in subsys level. We can
move init_kprobes() in core or pure level safely.

Thank you,

Masami Hiramatsu <>

 \ /
  Last update: 2019-05-22 09:30    [W:0.067 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site