Re: Ftrace startup test and boot-time tracing

2020-12-07 Thread Steven Rostedt
On Tue, 8 Dec 2020 08:26:49 +0900 Masami Hiramatsu wrote: > Hi Steve, > > On Mon, 7 Dec 2020 15:25:40 -0500 > Steven Rostedt wrote: > > > On Mon, 7 Dec 2020 23:02:59 +0900 > > Masami Hiramatsu wrote: > > > > > There will be the 2 options, one is to change kconfig so that user can not > >

Re: Ftrace startup test and boot-time tracing

2020-12-07 Thread Masami Hiramatsu
Hi Steve, On Mon, 7 Dec 2020 15:25:40 -0500 Steven Rostedt wrote: > On Mon, 7 Dec 2020 23:02:59 +0900 > Masami Hiramatsu wrote: > > > There will be the 2 options, one is to change kconfig so that user can not > > select FTRACE_STARTUP_TEST if BOOTTIME_TRACING=y, another is to provide > > a

Re: Ftrace startup test and boot-time tracing

2020-12-07 Thread Steven Rostedt
On Mon, 7 Dec 2020 23:02:59 +0900 Masami Hiramatsu wrote: > There will be the 2 options, one is to change kconfig so that user can not > select FTRACE_STARTUP_TEST if BOOTTIME_TRACING=y, another is to provide > a flag from trace_boot and all tests checks the flag at runtime. > (moreover, that

Ftrace startup test and boot-time tracing

2020-12-07 Thread Masami Hiramatsu
Hi Steve, I found that if I enabled the CONFIG_FTRACE_STARTUP_TEST=y and booted the kernel with kprobe-events defined by boot-time tracing, a warning output. [ 59.803496] trace_kprobe: Testing kprobe tracing: [ 59.804258] [ cut here ] [ 59.805682] WARNING: CPU: 3