linux-kernel - Re: [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace formats

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]

Date:	Sun, 13 Sep 2009 16:59:31 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Tom Zanussi <tzanussi@...il.com>
Subject: Re: [PATCH 0/6] [GIT PULL] tracing: automate output for ftrace
	formats


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

> Ingo,
> 
> Currently, the output for the format files for the internal ftrace
> plugin entries is done by hand. This becomes difficult to maintain
> and error prone. If a change happens to a structure, it is likely
> that it will not be shown in the format file which binary readers
> of ftrace require.
> 
> This patch series implements the logic that is used by TRACE_EVENT
> to use macros that create the structures and those same macros also
> show the output layout in the format files. This guarantees that the
> structures and the output formats remain in-sync.
> 
> Again, this is based off of tip/tracing/core2
> 
> Please pull the latest tip/tracing/core3 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core3

Pulled, thanks a lot Steve!

	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/