mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jack Daniel <wanders.thirst@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	Jiri Olsa <jolsa@redhat.com>,
	fweisbec@gmail.com
Subject: Re: latency tracing in mainline or rt
Date: Fri, 24 Sep 2010 12:26:49 -0400	[thread overview]
Message-ID: <1285345609.31083.19.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <AANLkTikjk-Wqz-dAi4Ozy=PSL7n1-sfrRhrP6GwjavA3@mail.gmail.com>

On Fri, 2010-09-24 at 21:44 +0530, Jack Daniel wrote:
> Hi,
> 
> Can some one tell me the difference between Latency tracing that's
> here http://people.redhat.com/mingo/latency-tracing-patches/ and the
> tracing supported in the RT kernel here
> http://www.kernel.org/pub/linux/kernel/projects/rt/ ? What's the
> status of the present latency tracing and its documentation. Does
> Ftrace override these with its superior tracing? Any help is highly
> appreciated.

Ftrace was derived from two projects. One was my own logdev, and the
other was Ingo's latency tracing patches. The irq/preempt off tracers
still hold some of the code from the latency tracing patches practically
untouched.

With the old latency tracing patches, to enable or disable the tracing
feature, you had to change a config option and recompile the kernel.

With ftrace, you only need to 

  echo irqsoff > /sys/kernel/debug/current_tracer

to enable irqsoff tracing (the latency of the kernel where it disables
interrupts).

Please read the documentation in the kernel source
Documentation/trace/ftrace.txt.

To answer your questions, ftrace is really just latency-tracing next
generation ;-)

-- Steve



      reply	other threads:[~2010-09-24 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 16:14 Jack Daniel
2010-09-24 16:26 ` Steven Rostedt [this message]

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=1285345609.31083.19.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=wanders.thirst@gmail.com \
    /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

all inboxes | Powered by JetHome®