lkml.org 
[lkml]   [2010]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Tracing configuration review
On Tue, 25 May 2010 17:09:59 -0400 Chase Douglas wrote:

> On Tue, 2010-05-25 at 22:13 +0200, Frederic Weisbecker wrote:
> > On Tue, May 25, 2010 at 03:31:46PM -0400, Chase Douglas wrote:
> > > The following options are what I am looking to set for our x86
> > > configurations. I've only included those that I am not 100% sure of.
> > > Comments are what I could gather from documentation and Kconfig, but
> > > they may not be accurate:
>
> <snip>
>
> > > # CONFIG_SCHED_TRACER is not set (headed for deprecation?)
> >
> >
> > We want to deprecate it in the long term, but for now we
> > don't have any replacement. Cool for RT latency tracing.
>
> I thought that the functionality is the same as what you get by:
>
> echo 1 > (debufs)/tracing/events/sched/enable
>
> > > CONFIG_KSYM_TRACER=y (no performance impact by default)
> >
> >
> > IMO, it is deprecated. The perf interface is much more powerful and flexible.
> > Prasad, do you agree if I remove this ftrace plugin?
>
> If there isn't any use in enabling it due to perf's features, then we
> can turn it off. However, if there's any use to be gained by this over
> perf's features, then I'd prefer to leave it on. Thoughts?
>
>
> > > CONFIG_WORKQUEUE_TRACER=y (no performance impact by default)
> >
> >
> > In the way for deprecation.
>
> Is this like the KMEM_TRACER where trace events have superseded it?


Hi Chase,

Would you mind sharing your final tracing config options?

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***


\
 
 \ /
  Last update: 2010-06-08 19:39    [W:0.124 / U:3.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site