Hello.
I get the following splat when booting a kernel with CONFIG_DYNAMIC_FTRACE on a mips
without a Coherency Manager.
[ 0.111734] ------------[ cut here ]------------
[ 0.116268] WARNING: CPU: 0 PID: 0 at kernel/smp.c:417 smp_call_function_many+0x124/0x370()
[ 0.124550] Modules linked in:
[ 0.127603] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.3.0-rc7 #10
[ 0.133838] Stack : 00000000 00000000 8081663a 00000037 80810000 00000000 0000000b 00000000
8069a4e8 80739ac7 80739fc0 00000000 00000000 80804b40 8071de60 80736638
00000000 800909dc 8074832c 80748330 000001a1 00000000 806a2a40 8071dd6c
8071de60 80114824 00000000 800909dc 80810000 00000082 8071dd6c 8069a4e8
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
[ 0.169252] Call Trace:
[ 0.171700] [<80020394>] show_stack+0x94/0xb0
[ 0.176049] [<8032c3a4>] dump_stack+0x64/0x90
[ 0.180394] [<80041e7c>] warn_slowpath_common+0xa4/0xe0
[ 0.185581] [<80041edc>] warn_slowpath_null+0x24/0x30
[ 0.190615] [<800b9ea4>] smp_call_function_many+0x124/0x370
[ 0.196172] [<8003c00c>] r4k_flush_icache_range+0x26c/0x274
[ 0.201732] [<80025310>] ftrace_modify_code+0x30/0x50
[ 0.206773] [<80799d88>] ftrace_dyn_arch_init+0x58/0x6c
[ 0.211976] [<807a31e4>] ftrace_init+0x24/0x134
[ 0.216481] [<80793cb0>] start_kernel+0x50c/0x530
[ 0.221161]
[ 0.222700] ---[ end trace cb88537fdc8fa200 ]---
[ 0.227370] ftrace: allocating 17221 entries in 34 pages
the splat started showing up after the following patch:
cccf34e9411c ("MIPS: c-r4k: Fix cache flushing for MT cores")
Looking at the call trace, the kernel has just started (only CPU0 running),
and ftrace_init is called.
ftrace_init -> local_irq_save -> ftrace_dyn_arch_init ->
ftrace_modify_code -> flush_icache_range -> r4k_flush_icache_range ->
r4k_on_each_cpu(local_r4k_flush_icache_range_ipi, &args);
r4k_on_each_cpu calls (since the patch above) smp_call_function_many,
with in turn has a WARN_ON_ONCE if irqs_disabled.
One could replace flush_icache_range with flush_icache_all in all
mips ftrace_modify_code variants, which would make the splat go away,
but is this performance decrease acceptable?
I also found an old mail mentioning this problem
http://www.linux-mips.org/archives/linux-mips/2010-08/msg00176.html
Interestingly, mips appears to be the only arch which implements
ftrace_dyn_arch_init, all others just "return 0", so mips is the only arch
that sends IPI:s in ftrace_dyn_arch_init.
I'm not sure, but I think that ftrace_init -> ftrace_process_locs
local_irq_save -> ftrace_update_code -> __ftrace_replace_code ->
ftrace_make_nop -> ftrace_modify_code -> flush_icache_range
is also possible during start up,
so refactoring away ftrace_dyn_arch_init probably won't
make sure that we don't get the splat anymore.
