TRACE_REMOTE relies on tracefs, eventfs and ring-buffer which are only built and declared when TRACING is enabled. It is however possible for a config to have FTRACE=y TRACING=n and TRACE_REMOTE=y.
To fix this configuration, have TRACE_REMOTE select TRACING directly, just like other FTRACE options do and drop the TRACING dependency from NVHE_EL2_TRACING to avoid a circular Kconfig dependency. Cc: [email protected] Fixes: ea908a2b79c8 ("tracing: Add a trace remote module for testing") Reported-by: kernel test robot <[email protected]> Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/ Signed-off-by: Vincent Donnefort <[email protected]> --- arch/arm64/kvm/Kconfig | 2 +- kernel/trace/Kconfig | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm64/kvm/Kconfig b/arch/arm64/kvm/Kconfig index 449154f9a485..e179b8ad79e8 100644 --- a/arch/arm64/kvm/Kconfig +++ b/arch/arm64/kvm/Kconfig @@ -74,7 +74,7 @@ if NVHE_EL2_DEBUG config NVHE_EL2_TRACING bool - depends on TRACING && FTRACE + depends on FTRACE select TRACE_REMOTE default y diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 0ab5916575a9..6587450cfcd1 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -1329,6 +1329,7 @@ source "kernel/trace/rv/Kconfig" config TRACE_REMOTE bool + select TRACING config SIMPLE_RING_BUFFER bool base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907 -- 2.56.0.385.gd3acb90ef8-goog
