public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <srostedt@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for tip] ftrace: remove latency_trace document
Date: Sun, 8 Mar 2009 16:41:51 +0100	[thread overview]
Message-ID: <20090308154151.GC19658@elte.hu> (raw)
In-Reply-To: <2f11576a0903071926u3eeb793fx44300a0257439535@mail.gmail.com>


* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:

> 2009/3/8 Frederic Weisbecker <fweisbec@gmail.com>:
> > On Sat, Mar 07, 2009 at 11:53:40PM +0900, KOSAKI Motohiro wrote:
> >> Subject: [PATCH] remove latency_trace document
> >>
> >> Currently, there aren't "Latency tracer" and latency_trace file.
> >> Then, its documentation is removed too.
> >
> > Hi,
> >
> > The latency_trace file has been removed but the latency tracing stil exists.
> > It has become an option instead of a file now:
> >
> > echo latency-format > /debugfs/tracing/trace_options
> >
> > There are even some tracers that default enable it (irqsoff, preemptoff...)
> > IMO, the documentation about latency tracing shouldn't be removed but
> > just updated a bit to reflect this change.
> 
> Ah, sorry.
> I totally misunderstood it.
> 
> thanks to correct my fault.

You are correct to point out that the documentation about 
latency tracing does need to be updated - as there's no 
latency_trace file anymore and we reference it in a few places:

Documentation/ftrace.txt:  latency_trace:
Documentation/ftrace.txt:	is retrieved. Unlike the "trace" and "latency_trace"
Documentation/ftrace.txt:	"latency_trace" files are static, and if the
Documentation/ftrace.txt:	"trace" or "latency_trace".  A new max trace will
Documentation/ftrace.txt:	trace via the latency_trace file.
Documentation/ftrace.txt:For traces that display latency times, the latency_trace file
Documentation/ftrace.txt:	latency_trace file is relative to the start of the trace.
Documentation/ftrace.txt:  verbose - This deals with the latency_trace file.
Documentation/ftrace.txt:		trace,trace_pipe,latency_trace. Example:
Documentation/ftrace.txt: # cat /debug/tracing/latency_trace
Documentation/ftrace.txt: # cat /debug/tracing/latency_trace
Documentation/ftrace.txt: # cat /debug/tracing/latency_trace
Documentation/ftrace.txt: # cat /debug/tracing/latency_trace

	Ingo

      reply	other threads:[~2009-03-08 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07 14:53 [PATCH for tip] ftrace: remove latency_trace document KOSAKI Motohiro
2009-03-07 14:55 ` [PATCH] ftrace: fix documentaion typo s/trace_max_latency/tracing_max_latency/ KOSAKI Motohiro
2009-03-08 15:52   ` [tip:tracing/doc] ftrace: fix documentation " KOSAKI Motohiro
2009-03-07 15:34 ` [PATCH for tip] ftrace: remove latency_trace document Frederic Weisbecker
2009-03-08  3:26   ` KOSAKI Motohiro
2009-03-08 15:41     ` Ingo Molnar [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=20090308154151.GC19658@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.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