From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: [PATCH v2] kgdb: Do not allow function tracing of kgdb code
Date: Wed, 25 Apr 2012 11:23:52 -0400 [thread overview]
Message-ID: <1335367432.28106.167.camel@gandalf.stny.rr.com> (raw)
As function tracing the kgdb code can cause issues, as kgdb is a
debugger itself, do not trace the kgdb functions.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
v2 - added all files in kernel/debug
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 532d2e0..b7828ce 100644
--- a/arch/x86/kernel/Makefile
+++ b/arch/x86/kernel/Makefile
@@ -15,6 +15,7 @@ CFLAGS_REMOVE_pvclock.o = -pg
CFLAGS_REMOVE_kvmclock.o = -pg
CFLAGS_REMOVE_ftrace.o = -pg
CFLAGS_REMOVE_early_printk.o = -pg
+CFLAGS_REMOVE_kgdb.o = -pg
endif
obj-y := process_$(BITS).o signal.o entry_$(BITS).o
diff --git a/kernel/debug/Makefile b/kernel/debug/Makefile
index a85edc3..5fa453c 100644
--- a/kernel/debug/Makefile
+++ b/kernel/debug/Makefile
@@ -2,5 +2,11 @@
# Makefile for the linux kernel debugger
#
+# Do not function trace debug files
+ifdef CONFIG_FUNCTION_TRACER
+ORIG_CFLAGS := $(KBUILD_CFLAGS)
+KBUILD_CFLAGS = $(subst -pg,,$(ORIG_CFLAGS))
+endif
+
obj-$(CONFIG_KGDB) += debug_core.o gdbstub.o
obj-$(CONFIG_KGDB_KDB) += kdb/
next reply other threads:[~2012-04-25 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 15:23 Steven Rostedt [this message]
2012-04-25 15:27 ` Jason Wessel
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=1335367432.28106.167.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=hpa@linux.intel.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®