* [PATCH] riscv: Stop supporting static ftrace
@ 2025-07-16 12:05 Alexandre Ghiti
2025-07-16 20:00 ` patchwork-bot+linux-riscv
0 siblings, 1 reply; 2+ messages in thread
From: Alexandre Ghiti @ 2025-07-16 12:05 UTC (permalink / raw)
To: Steven Rostedt, Paul Walmsley, Palmer Dabbelt, Albert Ou,
Alexandre Ghiti, Andy Chiu, Björn Töpel
Cc: linux-riscv, linux-kernel, chenmiao, kernel test robot,
Alexandre Ghiti
Now that DYNAMIC_FTRACE was introduced, there is no need to support
static ftrace as it is way less performant. This simplifies the code and
prevents build failures as reported by kernel test robot when
!DYNAMIC_FTRACE.
Also make sure that FUNCTION_TRACER can only be selected if
DYNAMIC_FTRACE is supported (we have a dependency on the toolchain).
Co-developed-by: chenmiao <chenmiao.ku@gmail.com>
Signed-off-by: chenmiao <chenmiao.ku@gmail.com>
Fixes: b2137c3b6d7a ("riscv: ftrace: prepare ftrace for atomic code patching")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202506191949.o3SMu8Zn-lkp@intel.com/
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
---
arch/riscv/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index d71ea0f4466fc3eefd1bd89f37637193d9a464da..1c5544401530fed9ecade4dd11c1c33a0bd6a2da 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -98,6 +98,7 @@ config RISCV
select CLONE_BACKWARDS
select COMMON_CLK
select CPU_PM if CPU_IDLE || HIBERNATION || SUSPEND
+ select DYNAMIC_FTRACE if FUNCTION_TRACER
select EDAC_SUPPORT
select FRAME_POINTER if PERF_EVENTS || (FUNCTION_TRACER && !DYNAMIC_FTRACE)
select FTRACE_MCOUNT_USE_PATCHABLE_FUNCTION_ENTRY if DYNAMIC_FTRACE
@@ -162,7 +163,7 @@ config RISCV
select HAVE_FTRACE_MCOUNT_RECORD if !XIP_KERNEL
select HAVE_FUNCTION_GRAPH_TRACER if HAVE_DYNAMIC_FTRACE_WITH_ARGS
select HAVE_FUNCTION_GRAPH_FREGS
- select HAVE_FUNCTION_TRACER if !XIP_KERNEL
+ select HAVE_FUNCTION_TRACER if !XIP_KERNEL && HAVE_DYNAMIC_FTRACE
select HAVE_EBPF_JIT if MMU
select HAVE_GUP_FAST if MMU
select HAVE_FUNCTION_ARG_ACCESS_API
---
base-commit: 5bd6225da2e2d8bbf2b6713fde42159f85ad3fdb
change-id: 20250716-dev-alex-static_ftrace-882f0d8357bf
Best regards,
--
Alexandre Ghiti <alexghiti@rivosinc.com>
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] riscv: Stop supporting static ftrace
2025-07-16 12:05 [PATCH] riscv: Stop supporting static ftrace Alexandre Ghiti
@ 2025-07-16 20:00 ` patchwork-bot+linux-riscv
0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+linux-riscv @ 2025-07-16 20:00 UTC (permalink / raw)
To: Alexandre Ghiti
Cc: linux-riscv, rostedt, paul.walmsley, palmer, aou, alex, andybnac,
bjorn, linux-kernel, chenmiao.ku, lkp
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@dabbelt.com>:
On Wed, 16 Jul 2025 12:05:16 +0000 you wrote:
> Now that DYNAMIC_FTRACE was introduced, there is no need to support
> static ftrace as it is way less performant. This simplifies the code and
> prevents build failures as reported by kernel test robot when
> !DYNAMIC_FTRACE.
>
> Also make sure that FUNCTION_TRACER can only be selected if
> DYNAMIC_FTRACE is supported (we have a dependency on the toolchain).
>
> [...]
Here is the summary with links:
- riscv: Stop supporting static ftrace
https://git.kernel.org/riscv/c/5874ca4c6280
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-07-16 19:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-16 12:05 [PATCH] riscv: Stop supporting static ftrace Alexandre Ghiti
2025-07-16 20:00 ` patchwork-bot+linux-riscv
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).