tracing: mark user_events as BROKEN

[linux-2.6-microblaze.git] / kernel / trace / Kconfig

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index a5eb5e7..2c43e32 100644 (file)
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -10,6 +10,17 @@ config USER_STACKTRACE_SUPPORT
 config NOP_TRACER
        bool
 
+config HAVE_RETHOOK
+       bool
+
+config RETHOOK
+       bool
+       depends on HAVE_RETHOOK
+       help
+         Enable generic return hooking feature. This is an internal
+         API, which will be used by other function-entry hooking
+         features like fprobe and kprobes.
+
 config HAVE_FUNCTION_TRACER
        bool
        help
@@ -236,6 +247,21 @@ config DYNAMIC_FTRACE_WITH_ARGS
        depends on DYNAMIC_FTRACE
        depends on HAVE_DYNAMIC_FTRACE_WITH_ARGS
 
+config FPROBE
+       bool "Kernel Function Probe (fprobe)"
+       depends on FUNCTION_TRACER
+       depends on DYNAMIC_FTRACE_WITH_REGS
+       depends on HAVE_RETHOOK
+       select RETHOOK
+       default n
+       help
+         This option enables kernel function probe (fprobe) based on ftrace.
+         The fprobe is similar to kprobes, but probes only for kernel function
+         entries and exits. This also can probe multiple functions by one
+         fprobe.
+
+         If unsure, say N.
+
 config FUNCTION_PROFILER
        bool "Kernel function profiler"
        depends on FUNCTION_TRACER
@@ -737,6 +763,21 @@ config SYNTH_EVENTS
 
          If in doubt, say N.
 
+config USER_EVENTS
+       bool "User trace events"
+       select TRACING
+       select DYNAMIC_EVENTS
+       depends on BROKEN || COMPILE_TEST # API needs to be straighten out
+       help
+         User trace events are user-defined trace events that
+         can be used like an existing kernel trace event.  User trace
+         events are generated by writing to a tracefs file.  User
+         processes can determine if their tracing events should be
+         generated by memory mapping a tracefs file and checking for
+         an associated byte being non-zero.
+
+         If in doubt, say N.
+
 config HIST_TRIGGERS
        bool "Histogram triggers"
        depends on ARCH_HAVE_NMI_SAFE_CMPXCHG