xen/tracing: it looks like we wanted CONFIG_FTRACE
authorJeremy Fitzhardinge <jeremy@goop.org>
Wed, 3 Aug 2011 16:43:44 +0000 (09:43 -0700)
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thu, 4 Aug 2011 19:31:27 +0000 (15:31 -0400)
Apparently we wanted CONFIG_FTRACE rather the CONFIG_FUNCTION_TRACER.

Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
Tested-by: Sander Eikelenboom <linux@eikelenboom.it>
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
arch/x86/xen/Makefile

index 45e94aca5bcef5aed5546c4a0cd25e1de5521e4e..3326204e251f3108650944ef1d558c98745c1935 100644 (file)
@@ -15,7 +15,7 @@ obj-y         := enlighten.o setup.o multicalls.o mmu.o irq.o \
                        grant-table.o suspend.o platform-pci-unplug.o \
                        p2m.o
 
-obj-$(CONFIG_FUNCTION_TRACER) += trace.o
+obj-$(CONFIG_FTRACE) += trace.o
 
 obj-$(CONFIG_SMP)              += smp.o
 obj-$(CONFIG_PARAVIRT_SPINLOCKS)+= spinlock.o