On Tue, 4 Dec 2018 at 23:33, Steven Rostedt wrote:
>
> On Tue, 4 Dec 2018 20:40:44 +0100
> Anders Roxell wrote:
>
> > When running in qemu on an kernel built with allmodconfig and debug
> > options (in particular kcov and ubsan) enabled, ftrace_replace_code
> > function call take minutes. The
On Tue, 4 Dec 2018 at 23:33, Steven Rostedt wrote:
>
> On Tue, 4 Dec 2018 20:40:44 +0100
> Anders Roxell wrote:
>
> > When running in qemu on an kernel built with allmodconfig and debug
> > options (in particular kcov and ubsan) enabled, ftrace_replace_code
> > function call take minutes. The
On Tue, 4 Dec 2018 20:40:44 +0100
Anders Roxell wrote:
> When running in qemu on an kernel built with allmodconfig and debug
> options (in particular kcov and ubsan) enabled, ftrace_replace_code
> function call take minutes. The ftrace selftest calls
> ftrace_replace_code to look >4 through
On Tue, 4 Dec 2018 20:40:44 +0100
Anders Roxell wrote:
> When running in qemu on an kernel built with allmodconfig and debug
> options (in particular kcov and ubsan) enabled, ftrace_replace_code
> function call take minutes. The ftrace selftest calls
> ftrace_replace_code to look >4 through
When running in qemu on an kernel built with allmodconfig and debug
options (in particular kcov and ubsan) enabled, ftrace_replace_code
function call take minutes. The ftrace selftest calls
ftrace_replace_code to look >4 through
ftrace_make_call/ftrace_make_nop, and these end up calling
When running in qemu on an kernel built with allmodconfig and debug
options (in particular kcov and ubsan) enabled, ftrace_replace_code
function call take minutes. The ftrace selftest calls
ftrace_replace_code to look >4 through
ftrace_make_call/ftrace_make_nop, and these end up calling
6 matches
Mail list logo