From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chase Douglas <chase.douglas@canonical.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Tracing configuration review
Date: Wed, 26 May 2010 01:13:10 +0200 [thread overview]
Message-ID: <20100525231308.GE5370@nowhere> (raw)
In-Reply-To: <1274824866.1876.1.camel@localhost>
On Tue, May 25, 2010 at 06:01:06PM -0400, Steven Rostedt wrote:
> On Tue, 2010-05-25 at 22:17 +0200, Frederic Weisbecker wrote:
> > On Tue, May 25, 2010 at 03:46:08PM -0400, Steven Rostedt wrote:
> > > On Tue, 2010-05-25 at 15:31 -0400, Chase Douglas wrote:
> > > > # CONFIG_SCHED_TRACER is not set (headed for deprecation?)
> > >
> > > Although it is headed for deprecation, I think it still gets set by
> > > other tracers, since it has the code to initiate the comm reader.
> >
> >
> >
> > Doesn't actually CONTEXT_SWITCH_TRACER has the code for the
> > comm things?
> >
>
> Ah, I was confused. But then the SCHED_TRACER is the wakeup tracer, and
> that is heading for deprecation??
It would be nice if we can make it a ftrace_event_call, so that we
can control it like any other trace event.
But for now we don't have any replacement, so it is not yet deprecated.
That's why I said "in the long term" ;)
next prev parent reply other threads:[~2010-05-25 23:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 19:31 Tracing configuration review Chase Douglas
2010-05-25 19:46 ` Steven Rostedt
2010-05-25 19:58 ` Chase Douglas
2010-05-25 20:20 ` Frederic Weisbecker
2010-05-25 20:17 ` Frederic Weisbecker
2010-05-25 22:01 ` Steven Rostedt
2010-05-25 23:13 ` Frederic Weisbecker [this message]
2010-05-26 10:57 ` [Patch] tracing: remove boot tracer Américo Wang
2010-05-26 15:49 ` Frederic Weisbecker
2010-05-25 20:13 ` Tracing configuration review Frederic Weisbecker
2010-05-25 21:09 ` Chase Douglas
2010-05-25 23:06 ` Frederic Weisbecker
2010-05-27 11:20 ` K.Prasad
2010-05-27 22:15 ` Frederic Weisbecker
2010-06-08 17:35 ` Randy Dunlap
2010-06-08 22:00 ` Chase Douglas
2010-06-11 21:51 ` Randy Dunlap
2010-06-14 2:41 ` Chase Douglas
2010-05-26 6:19 ` Pekka Enberg
2010-05-26 7:20 ` Li Zefan
2010-05-26 7:44 ` Pekka Enberg
2010-05-26 8:42 ` Eduard - Gabriel Munteanu
2010-05-26 9:12 ` 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=20100525231308.GE5370@nowhere \
--to=fweisbec@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.