Re: [PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set

2018-06-04 Thread Alan Kao
Hi Palmer, Thanks for the refining work! But a small correction here: On Mon, Jun 04, 2018 at 01:30:28PM -0700, Palmer Dabbelt wrote: > From: Alan Kao > > The EXPORT_SYMBOL(_mcount) for RISC-V ended up inside a > CONFIG_FUNCTION_GRAPH_TRACER ifdef. If you enable modules without > enabling

Re: [PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set

2018-06-04 Thread Alan Kao
Hi Palmer, Thanks for the refining work! But a small correction here: On Mon, Jun 04, 2018 at 01:30:28PM -0700, Palmer Dabbelt wrote: > From: Alan Kao > > The EXPORT_SYMBOL(_mcount) for RISC-V ended up inside a > CONFIG_FUNCTION_GRAPH_TRACER ifdef. If you enable modules without > enabling

[PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set

2018-06-04 Thread Palmer Dabbelt
From: Alan Kao The EXPORT_SYMBOL(_mcount) for RISC-V ended up inside a CONFIG_FUNCTION_GRAPH_TRACER ifdef. If you enable modules without enabling CONFIG_FUNCTION_GRAPH_TRACER then you'll get a build error without this patch because the modules won't be able to find _mcount. The new behavior is

[PATCH] riscv/ftrace: Export _mcount when FUNCTION_GRAPH_TRACER isn't set

2018-06-04 Thread Palmer Dabbelt
From: Alan Kao The EXPORT_SYMBOL(_mcount) for RISC-V ended up inside a CONFIG_FUNCTION_GRAPH_TRACER ifdef. If you enable modules without enabling CONFIG_FUNCTION_GRAPH_TRACER then you'll get a build error without this patch because the modules won't be able to find _mcount. The new behavior is