From: tip-bot for Li Zefan <lizf@cn.fujitsu.com>
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, lizf@cn.fujitsu.com,
tglx@linutronix.de
Subject: [tip:tracing/core] tracing: Remove CONFIG_TRACE_POWER from kernel config
Date: Fri, 26 Feb 2010 09:28:06 GMT [thread overview]
Message-ID: <tip-1ab83a89411556c4d5914dcf0d5da190178ae7db@git.kernel.org> (raw)
In-Reply-To: <4B84D50E.4070806@cn.fujitsu.com>
Commit-ID: 1ab83a89411556c4d5914dcf0d5da190178ae7db
Gitweb: http://git.kernel.org/tip/1ab83a89411556c4d5914dcf0d5da190178ae7db
Author: Li Zefan <lizf@cn.fujitsu.com>
AuthorDate: Wed, 24 Feb 2010 15:28:14 +0800
Committer: Steven Rostedt <rostedt@goodmis.org>
CommitDate: Thu, 25 Feb 2010 10:31:45 -0500
tracing: Remove CONFIG_TRACE_POWER from kernel config
The power tracer has been converted to power trace events.
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
LKML-Reference: <4B84D50E.4070806@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/Kconfig | 9 ---------
1 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 6c22d8a..ca2d3a8 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -330,15 +330,6 @@ config BRANCH_TRACER
Say N if unsure.
-config POWER_TRACER
- bool "Trace power consumption behavior"
- depends on X86
- select GENERIC_TRACER
- help
- This tracer helps developers to analyze and optimize the kernel's
- power management decisions, specifically the C-state and P-state
- behavior.
-
config KSYM_TRACER
bool "Trace read and write access on kernel memory locations"
depends on HAVE_HW_BREAKPOINT
prev parent reply other threads:[~2010-02-26 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 7:28 [PATCH] " Li Zefan
2010-02-25 4:00 ` Frederic Weisbecker
2010-02-25 15:27 ` Steven Rostedt
2010-02-26 9:28 ` tip-bot for Li Zefan [this message]
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-1ab83a89411556c4d5914dcf0d5da190178ae7db@git.kernel.org \
--to=lizf@cn.fujitsu.com \
--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
Powered by JetHome