tracing/remotes: Fix TRACE_REMOTE build when TRACING=n

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: stable@vger.kernel.org
Fixes: ea908a2b79 ("tracing: Add a trace remote module for testing")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202610142301.GBepPVmS-lkp@intel.com/
Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
Link: https://patch.msgid.link/20261015112814.332084-1-vdonnefort@google.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
This commit is contained in:
Vincent Donnefort 2026-10-15 12:28:14 +01:00 committed by Marc Zyngier
parent 7ad25ad110
commit 3bb853ad84
2 changed files with 2 additions and 1 deletions

View File

@ -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

View File

@ -1329,6 +1329,7 @@ source "kernel/trace/rv/Kconfig"
config TRACE_REMOTE
bool
select TRACING
config SIMPLE_RING_BUFFER
bool