On Tue, 21 May 2019 16:56:16 +0900 Masami Hiramatsu <mhiramat@xxxxxxxxxx> wrote: > Note that 'trace_event=' option enables trace event at very early > timing, but the events added by 'kprobe_event=' are enabled right > before enabling device drivers at this point. It is enough for > tracing device driver initialization etc. Nice! I wonder if we can have this called before the trace_event boot is analyzed. Then have the kprobe_event work more like the kprobe_events file, and not enable the kprobes but only create them. If you want to enable them you do a trace_event=kprobes as well. Perhaps we could enable kprobes at early init? What do you think? Or is there something else in kprobes that prevents such an early enabling of it? -- Steve
