From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] tracing: Fix TRACING_SUPPORT dependency
Date: Fri, 20 Mar 2009 18:09:14 +0300 [thread overview]
Message-ID: <20090320150914.GA22769@oksana.dev.rtsoft.ru> (raw)
commit 40ada30f9621fbd831ac2437b9a2a399aad34b00 ("tracing: clean up
menu"), despite the "clean up" in its purpose, introduced behavioural
change for Kconfig symbols: we no longer able to select tracing
support on PPC32 (because IRQFLAGS_SUPPORT isn't yet implemented).
The IRQFLAGS_SUPPORT is not mandatory for most tracers, tracing core
has a special case for platforms w/o irqflags (which, by the way, has
become useless as of the commit above).
This patch restores the old behaviour, and thus brings the tracing
back on PPC32.
p.s.
The IRQSOFF_TRACER (which is the only tracer that requires IRQFLAGS
support) still depends on TRACE_IRQFLAGS_SUPPORT Kconfig symbol.
Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
---
kernel/trace/Kconfig | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index ee70841..774aba7 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -63,7 +63,6 @@ config TRACING
#
config TRACING_SUPPORT
bool
- depends on TRACE_IRQFLAGS_SUPPORT
depends on STACKTRACE_SUPPORT
default y
--
1.5.6.5
next reply other threads:[~2009-03-20 15:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 15:09 Anton Vorontsov [this message]
2009-03-20 19:04 ` [PATCH] tracing: Fix TRACING_SUPPORT dependency Ingo Molnar
2009-03-20 19:04 ` Ingo Molnar
2009-03-20 19:39 ` Anton Vorontsov
2009-03-20 19:39 ` Anton Vorontsov
2009-03-20 19:57 ` Ingo Molnar
2009-03-20 19:57 ` Ingo Molnar
2009-03-20 20:22 ` Anton Vorontsov
2009-03-20 20:22 ` Anton Vorontsov
2009-03-21 16:18 ` Ingo Molnar
2009-03-21 16:18 ` Ingo Molnar
2009-03-21 16:31 ` Steven Rostedt
2009-03-21 16:31 ` Steven Rostedt
2009-03-21 16:33 ` Ingo Molnar
2009-03-21 16:33 ` Ingo Molnar
2009-03-21 16:41 ` Steven Rostedt
2009-03-21 16:41 ` Steven Rostedt
2009-03-21 16:43 ` Steven Rostedt
2009-03-21 16:43 ` Steven Rostedt
2009-03-21 16:46 ` Ingo Molnar
2009-03-21 16:46 ` Ingo Molnar
2009-03-23 22:07 ` [PATCH] tracing: Fix TRACING_SUPPORT dependency for PPC32 Anton Vorontsov
2009-03-23 22:07 ` Anton Vorontsov
2009-03-23 22:24 ` [tip:tracing/ftrace] " Anton Vorontsov
2009-03-24 0:51 ` [PATCH] " Steven Rostedt
2009-03-24 0:51 ` Steven Rostedt
2009-03-24 5:43 ` [PATCH] tracing: Fix TRACING_SUPPORT dependency Benjamin Herrenschmidt
2009-03-24 5:43 ` Benjamin Herrenschmidt
2009-03-21 3:09 ` Steven Rostedt
2009-03-21 3:09 ` Steven Rostedt
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=20090320150914.GA22769@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.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.