linux-kernel - Re: [PATCH 0/3] ftrace: overrun accounting and trace

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]

Date:	Tue, 22 Apr 2008 15:33:44 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...l.org,
	Peter Zijlstra <peterz@...radead.org>,
	Soeren Sandmann Pedersen <sandmann@...hat.com>,
	Pekka Paalanen <pq@....fi>
Subject: Re: [PATCH 0/3] ftrace: overrun accounting and trace_pipe headers


* Steven Rostedt <rostedt@...dmis.org> wrote:

> The first patch in this series adds accounting to record overruns. 
> That is where the writing catches up to the reading of the buffer. 
> This really only matters for trace_pipe since that's a consumer / 
> producer output file.
> 
> The next patch adds new methods for the plugins to hook into the 
> open_pipe and open_read, to let a plugin produce a header. The 
> open_read method can also be used to do something when overruns are 
> detected.

thanks, applied.

> The last patch is a test patch AND SHOULD NOT BE APPLIED. It is just 
> an example in how to use the new methods to produce a header. It 
> simply makes the ftrace tracer produce a simple "Test header" before 
> any output.

thanks, not applied ;-)

	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/