From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Compile errors current linus tree with xen options enabled (seems related to jeremy's tracing changes)
Date: Wed, 03 Aug 2011 09:43:44 -0700 [thread overview]
Message-ID: <4E397AC0.5010700@goop.org> (raw)
In-Reply-To: <18210159243.20110803124316@eikelenboom.it>
On 08/03/2011 03:43 AM, Sander Eikelenboom wrote:
> Hi Jeremy/Konrad,
>
> I have tried to compile linus his tree git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) but i'm encountering compile errors.
> Switching of all "tracers" under "Kernel hacking" seems to circumvent these compile errors.
>
> .config which gives the build errors attached (a "make defconfig" for x86_64 with minimal changes for xen and hardware support)
Does this fix it?
J
>From 55a266630d0319c9eb4e0e067d4a0c7f27f978bd Mon Sep 17 00:00:00 2001
From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Tue, 2 Aug 2011 13:38:17 -0700
Subject: [PATCH] xen/tracing: it looks like we wanted CONFIG_FTRACE
Apparently we wanted CONFIG_FTRACE rather the CONFIG_FUNCTION_TRACER.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
diff --git a/arch/x86/xen/Makefile b/arch/x86/xen/Makefile
index ce69201..1894b4a 100644
--- a/arch/x86/xen/Makefile
+++ b/arch/x86/xen/Makefile
@@ -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
next prev parent reply other threads:[~2011-08-03 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:43 Compile errors current linus tree with xen options enabled (seems related to jeremy's tracing changes) Sander Eikelenboom
2011-08-03 16:43 ` Jeremy Fitzhardinge [this message]
2011-08-03 17:30 ` Sander Eikelenboom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E397AC0.5010700@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.