public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Arjan van de Ven <arjan@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Remove CONFIG_TRACE_POWER from kernel config
Date: Thu, 25 Feb 2010 05:00:37 +0100	[thread overview]
Message-ID: <20100225040035.GE7491@nowhere> (raw)
In-Reply-To: <4B84D50E.4070806@cn.fujitsu.com>

On Wed, Feb 24, 2010 at 03:28:14PM +0800, Li Zefan wrote:
> The power tracer has been converted to power trace events.
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>


Acked-by: Frederic Weisbecker <fweisbec@gmail.com>


> ---
>  kernel/trace/Kconfig |    9 ---------
>  1 files changed, 0 insertions(+), 9 deletions(-)
> 
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index 928b289..745d01c 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -341,15 +341,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
> -- 
> 1.6.3
> 


  reply	other threads:[~2010-02-25  4:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  7:28 [PATCH] tracing: Remove CONFIG_TRACE_POWER from kernel config Li Zefan
2010-02-25  4:00 ` Frederic Weisbecker [this message]
2010-02-25 15:27 ` Steven Rostedt
2010-02-26  9:28 ` [tip:tracing/core] " tip-bot for Li Zefan

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=20100225040035.GE7491@nowhere \
    --to=fweisbec@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --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