linux-kernel - Re: latency tracing in mainline or rt

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] [day] [month] [year] [list]

Message-ID: <1285345609.31083.19.camel@gandalf.stny.rr.com>
Date:	Fri, 24 Sep 2010 12:26:49 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jack Daniel <wanders.thirst@...il.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Jiri Olsa <jolsa@...hat.com>, fweisbec@...il.com
Subject: Re: latency tracing in mainline or rt

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


--
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/