diff options
| author |  Andy Chiu <andy.chiu@sifive.com>
| 2024-06-13 15:11:06 +0800 |
|---|---|---|
| committer |  Palmer Dabbelt <palmer@rivosinc.com>
| 2024-06-26 07:37:59 -0700 |
| commit | 23b2188920a25e88d447dd7d819a0b0f62fb4455 (patch) | |
| tree | 3d48089f37384eeec5f7512facf346726e9b1848 /drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | |
| parent | Linux 6.10-rc1 (diff) | |
| download | linux-23b2188920a25e88d447dd7d819a0b0f62fb4455.tar.gz linux-23b2188920a25e88d447dd7d819a0b0f62fb4455.tar.bz2 linux-23b2188920a25e88d447dd7d819a0b0f62fb4455.zip | |
riscv: stacktrace: convert arch_stack_walk() to noinstr
arch_stack_walk() is called intensively in function_graph when the
kernel is compiled with CONFIG_TRACE_IRQFLAGS. As a result, the kernel
logs a lot of arch_stack_walk and its sub-functions into the ftrace
buffer. However, these functions should not appear on the trace log
because they are part of the ftrace itself. This patch references what
arm64 does for the smae function. So it further prevent the re-enter
kprobe issue, which is also possible on riscv.
Related-to: commit 0fbcd8abf337 ("arm64: Prohibit instrumentation on arch_stack_walk()")
Fixes: 680341382da5 ("riscv: add CALLER_ADDRx support")
Signed-off-by: Andy Chiu <andy.chiu@sifive.com>
Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Link: https://lore.kernel.org/r/20240613-dev-andyc-dyn-ftrace-v4-v1-1-1a538e12c01e@sifive.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Diffstat (limited to 'drivers/pinctrl/bcm/pinctrl-iproc-gpio.c')
0 files changed, 0 insertions, 0 deletions