From: tip-bot for Michal Simek <monstr@monstr.eu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, rostedt@goodmis.org, monstr@monstr.eu,
tglx@linutronix.de
Subject: [tip:perf/urgent] ftrace: Build without frame pointers on Microblaze
Date: Wed, 27 Apr 2011 15:57:47 GMT [thread overview]
Message-ID: <tip-d20ac252821ab9780ddf00b95629547d3cebc857@git.kernel.org> (raw)
In-Reply-To: <1301908812-8119-2-git-send-email-monstr@monstr.eu>
Commit-ID: d20ac252821ab9780ddf00b95629547d3cebc857
Gitweb: http://git.kernel.org/tip/d20ac252821ab9780ddf00b95629547d3cebc857
Author: Michal Simek <monstr@monstr.eu>
AuthorDate: Mon, 4 Apr 2011 11:20:12 +0200
Committer: Steven Rostedt <rostedt@goodmis.org>
CommitDate: Thu, 21 Apr 2011 09:06:24 -0400
ftrace: Build without frame pointers on Microblaze
Microblaze doesn't need/support FRAME_POINTERS in order to have a working
function tracer.
The patch remove Kconfig warning.
Warning log:
warning: (LOCKDEP && FAULT_INJECTION_STACKTRACE_FILTER && LATENCYTOP &&
FUNCTION_TRACER && KMEMCHECK) selects FRAME_POINTER which has unmet direct
dependencies (DEBUG_KERNEL && (CRIS || M68K || FRV || UML || AVR32 ||
SUPERH || BLACKFIN || MN10300) || ARCH_WANT_FRAME_POINTERS)
Signed-off-by: Michal Simek <monstr@monstr.eu>
Link: http://lkml.kernel.org/r/1301908812-8119-2-git-send-email-monstr@monstr.eu
CC: Frederic Weisbecker <fweisbec@gmail.com>
CC: Ingo Molnar <mingo@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 61d7d59f..2ad39e5 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -141,7 +141,7 @@ if FTRACE
config FUNCTION_TRACER
bool "Kernel Function Tracer"
depends on HAVE_FUNCTION_TRACER
- select FRAME_POINTER if !ARM_UNWIND && !S390
+ select FRAME_POINTER if !ARM_UNWIND && !S390 && !MICROBLAZE
select KALLSYMS
select GENERIC_TRACER
select CONTEXT_SWITCH_TRACER
next prev parent reply other threads:[~2011-04-27 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 9:20 [PATCH] usb: Fix Kconfig unmet dependencies for Microblaze EHCI Michal Simek
2011-04-04 9:20 ` [PATCH] ftrace: Build without frame pointers on Microblaze Michal Simek
2011-04-14 6:48 ` Michal Simek
2011-04-21 2:17 ` Steven Rostedt
2011-04-21 5:42 ` Michal Simek
2011-04-27 15:57 ` tip-bot for Michal Simek [this message]
2011-04-04 9:26 ` [PATCH] usb: Fix Kconfig unmet dependencies for Microblaze EHCI Sergei Shtylyov
2011-04-04 9:31 ` Michal Simek
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=tip-d20ac252821ab9780ddf00b95629547d3cebc857@git.kernel.org \
--to=monstr@monstr.eu \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).