linux-kernel - Re: [PATCH for tip] ftrace: remove latency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090308154151.GC19658@elte.hu>
Date:	Sun, 8 Mar 2009 16:41:51 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <srostedt@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH for tip] ftrace: remove latency_trace document

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

> 2009/3/8 Frederic Weisbecker <fweisbec@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/