All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: andi@firstfloor.org, fweisbec@gmail.com, mingo@elte.hu,
	acme@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat
Date: Sun, 12 Jul 2009 15:24:05 +0200	[thread overview]
Message-ID: <1247405045.6733.2.camel@laptop> (raw)
In-Reply-To: <20090712.162337.287595819039280884.mitake@dcl.info.waseda.ac.jp>

On Sun, 2009-07-12 at 16:23 +0900, Hitoshi Mitake wrote:

> Thanks, I understood your advice. Using infrastructure of ftrace is good idea, so I'll use it.
> 
> But I have a question.
> I can't enable CONFIG_EVENT_PROFILE because it depends on CONFIG_EVENT_TRACER.
> And CONFIG_EVENT_TRACER seems something never enabled.
> 
> % git grep EVENT_TRACER
> arch/arm/configs/cm_x300_defconfig:# CONFIG_EVENT_TRACER is not set
> arch/arm/configs/davinci_all_defconfig:# CONFIG_EVENT_TRACER is not set
> arch/arm/configs/ep93xx_defconfig:# CONFIG_EVENT_TRACER is not set
> ....
> arch/x86/configs/i386_defconfig:# CONFIG_EVENT_TRACER is not set
> arch/x86/configs/x86_64_defconfig:# CONFIG_EVENT_TRACER is not set
> init/Kconfig:   depends on PERF_COUNTERS && EVENT_TRACER
> 
> In addition, this is the output of searching this on menuconfig
>     Symbol: EVENT_TRACER [=EVENT_TRACER]          
> and, there is a log in git
> 
> commit a7abe97fd8e7a6ccabba5a04a9f17be9211d418c
> Author: Steven Rostedt <srostedt@redhat.com>
> Date:   Mon Apr 20 10:59:34 2009 -0400
> 
>     tracing: rename EVENT_TRACER config to ENABLE_EVENT_TRACING
> 
>     Currently we have two configs: EVENT_TRACING and EVENT_TRACER.
>     All tracers enable EVENT_TRACING. The EVENT_TRACER is only a
>     convenience to enable the EVENT_TRACING when no other tracers
>     are enabled.
> 
> Does EVENT_TRACER make any sense?
> If doesn't, can I remove dependency of CONFIG_EVENT_PROFILE?

Yeah, steve broke it, but then Jason fixed it again, but his patches
might not have made it in yet.

  http://lkml.org/lkml/2009/7/6/313


  reply	other threads:[~2009-07-12 13:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  6:21 [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat Hitoshi Mitake
2009-07-01  7:31 ` Ingo Molnar
2009-07-01  8:21   ` Hitoshi Mitake
2009-07-01 13:45   ` Frederic Weisbecker
2009-07-01 13:50     ` Ingo Molnar
2009-07-01 14:17       ` mitake
2009-07-01  7:38 ` Andi Kleen
2009-07-01  8:42   ` Hitoshi Mitake
2009-07-01  9:07     ` Ingo Molnar
2009-07-01  9:42       ` Hitoshi Mitake
2009-07-01 11:06         ` Ingo Molnar
2009-07-01 12:53           ` Hitoshi Mitake
2009-07-01 15:44             ` Frederic Weisbecker
2009-07-06  5:20               ` mitake
2009-07-06  8:51                 ` Peter Zijlstra
2009-07-06 11:54                   ` Andi Kleen
2009-07-10 12:45                     ` mitake
2009-07-10 12:52                       ` Peter Zijlstra
2009-07-10 13:43                         ` Ingo Molnar
2009-07-10 13:46                           ` Frederic Weisbecker
2009-07-10 13:50                             ` Ingo Molnar
2009-07-10 13:56                               ` Peter Zijlstra
2009-07-12  7:23                         ` Hitoshi Mitake
2009-07-12 13:24                           ` Peter Zijlstra [this message]
2009-07-13  6:06                             ` Hitoshi Mitake
2009-07-13  8:51                               ` Ingo Molnar
2009-07-14  0:48                                 ` Hitoshi Mitake
2009-07-18 13:25                                   ` Ingo Molnar
2009-07-01 12:40       ` Andi Kleen
2009-07-01 13:50       ` [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat II Andi Kleen
2009-07-01  9:48     ` [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat Andi Kleen

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=1247405045.6733.2.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mitake@dcl.info.waseda.ac.jp \
    /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.