mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Albin Tonnerre <albin.tonnerre@free-electrons.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: srostedt@redhat.com, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] tracing: remove mentioning of legacy latency_trace file from documentation
Date: Mon, 31 Aug 2009 21:46:44 +0200	[thread overview]
Message-ID: <20090831194644.GD4237@pc-ras4041.res.insa> (raw)
In-Reply-To: <20090831190852.GC6048@nowhere>

On Mon, Aug 31, 2009 at 09:08:54PM +0200, Frederic Weisbecker wrote :
> On Mon, Aug 31, 2009 at 08:50:35PM +0200, Albin Tonnerre wrote:
> >  
> > @@ -307,8 +299,8 @@ the lowest priority thread (pid 0).
> >  Latency trace format
> >  --------------------
> >  
> > -For traces that display latency times, the latency_trace file
> > -gives somewhat more information to see why a latency happened.
> > +For traces that display latency times, the trace file gives
> > +somewhat more information to see why a latency happened.
> 
> 
> 
> Hmm, now that the latency_trace file has disappeared, this sentence
> doesn't make sens anymore.
> The trace file gives more information about latency than...? :-)
> 
> Actually the latency format still exists.
> It's toggable through the latency-format trace option:
> 
> echo latency-format > trace_options
> 
> I guess this documentation should actually not make the latency
> format documentation disappear but actually mirror the moving from
> a file to an option.

Right, I'll do that. Actually this patch doesn't really make it disappear, as
the format is still described here. I agree that the above paragraph should be
rephrased to mention that i's available through the latency-format option.

> >    delay: This is just to help catch your eye a bit better. And
> >  	 needs to be fixed to be only relative to the same CPU.
> > @@ -440,7 +432,8 @@ Here are the available options:
> >    sym-addr:
> >     bash-4000  [01]  1477.606694: simple_strtoul <c0339346>
> >  
> > -  verbose - This deals with the latency_trace file.
> > +  verbose - This deals with the trace file when it
> > +            displays lantecy times.
> 
> 
> "latency"

thanks

> Is it true when latency-format is not selected?

No, it only applies when latency-format is selected.

Regards,
-- 
Albin Tonnerre, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-08-31 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 18:50 Albin Tonnerre
2009-08-31 19:08 ` Frederic Weisbecker
2009-08-31 19:46   ` Albin Tonnerre [this message]
2009-08-31 20:40   ` [PATCH v2] " Albin Tonnerre
2009-09-04 15:41     ` Frederic Weisbecker
2009-09-06  4:36     ` [tip:tracing/core] tracing: Remove " tip-bot for Albin Tonnerre
2009-08-31 19:19 ` [PATCH] tracing: remove " Frederic Weisbecker
2009-08-31 19:40   ` Albin Tonnerre

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=20090831194644.GD4237@pc-ras4041.res.insa \
    --to=albin.tonnerre@free-electrons.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®