From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu
Cc: a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>,
rostedt@goodmis.org
Subject: [PATCH 2/2] perf: Enable function tracing for perf core
Date: Sat, 18 Aug 2012 09:15:30 -0700 [thread overview]
Message-ID: <1345306530-25665-2-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1345306530-25665-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
According to Steven R. there is no reason left to not support
function tracing for the perf core. This makes it easier to debug
perf.
Don't remove -pg for the x86 and generic perf core.
Cc: rostedt@goodmis.org
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
arch/x86/kernel/cpu/Makefile | 1 -
kernel/events/Makefile | 4 ----
2 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile
index d30a6a9..6a16725 100644
--- a/arch/x86/kernel/cpu/Makefile
+++ b/arch/x86/kernel/cpu/Makefile
@@ -5,7 +5,6 @@
# Don't trace early stages of a secondary CPU boot
ifdef CONFIG_FUNCTION_TRACER
CFLAGS_REMOVE_common.o = -pg
-CFLAGS_REMOVE_perf_event.o = -pg
endif
# Make sure load_percpu_segment has no stackprotector
diff --git a/kernel/events/Makefile b/kernel/events/Makefile
index 103f5d1..a630994 100644
--- a/kernel/events/Makefile
+++ b/kernel/events/Makefile
@@ -1,7 +1,3 @@
-ifdef CONFIG_FUNCTION_TRACER
-CFLAGS_REMOVE_core.o = -pg
-endif
-
obj-y := core.o ring_buffer.o callchain.o
obj-$(CONFIG_HAVE_HW_BREAKPOINT) += hw_breakpoint.o
--
1.7.7.6
next prev parent reply other threads:[~2012-08-18 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 16:15 [PATCH 1/2] pebs, x86: Make sure to really disable PEBS Andi Kleen
2012-08-18 16:15 ` Andi Kleen [this message]
2012-08-21 15:13 ` [PATCH 2/2] perf: Enable function tracing for perf core Steven Rostedt
2012-08-20 10:10 ` [PATCH 1/2] pebs, x86: Make sure to really disable PEBS Peter Zijlstra
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=1345306530-25665-2-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).