Skip to contentSkip to conversation

Tracing/ftrace: Give an entry on the config for initcall tracer

PATCH In review Frédéric Weisbecker 1 participant 1 message Sep 23, 2008 Tracing

lore
Share & tools
lore
#0 lore raw

PATCH 3/4 Tracing/ftrace: Give an entry on the config for initcall tracer

Bring the entry to choose the initcall tracer on the kernel config.

---

kernel/trace/Kconfig +10 -0
index 254328d..53952b7 100644
@@ -126,6 +126,16 @@ config STACK_TRACER
 	  This tracer records the max stack of the kernel, and displays
 	  it in debugfs/tracing/stack_trace
 
+config INITCALL_TRACER
+	bool "Trace initcalls"
+	depends on HAVE_FTRACE
+	depends on DEBUG_KERNEL
+	select TRACING
+	help
+	  This tracer records the initcalls which occur after SMP initialization. 
+	  Its aim is to be parsed by the /scripts/bootgraph.pl to produce a graph,
+	  giving a visual representation of the delays during initcalls.
+
 config DYNAMIC_FTRACE
 	bool "enable/disable ftrace tracepoints dynamically"
 	depends on FTRACE
kernel/trace/Makefile +1 -0
index 73ba13f..1d7cc74 100644
@@ -22,5 +22,6 @@ obj-$(CONFIG_SCHED_TRACER) += trace_sched_wakeup.o
 obj-$(CONFIG_NOP_TRACER) += trace_nop.o
 obj-$(CONFIG_STACK_TRACER) += trace_stack.o
 obj-$(CONFIG_MMIOTRACE) += trace_mmiotrace.o
+obj-$(CONFIG_INITCALL_TRACER) += trace_initcall.o
 
 libftrace-y := ftrace.o