Re: [PATCH][RFC] Adding information of counts processes acquiredhow many spinlocks to schedstat

From: Peter Zijlstra
Date: Sun Jul 12 2009 - 09:24:38 EST


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@xxxxxxxxxx>
> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/