linux-kernel - Re: [PATCH 00/12] perf trace: Python scripting support

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: <20100219213707.GA6991@nowhere>
Date:	Fri, 19 Feb 2010 22:37:12 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Tom Zanussi <tzanussi@...il.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, rostedt@...dmis.org,
	k-keiichi@...jp.nec.com, Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Paul Mackerras <paulus@...ba.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCH 00/12] perf trace: Python scripting support

On Wed, Jan 27, 2010 at 02:27:51AM -0600, Tom Zanussi wrote:
> This patchset adds a Python scripting engine to perf trace.  In the
> process, it also creates a scripting-engines directory under perf/util
> and moves the existing Perl support there, to avoid cluttering the
> main perf/util directory with scripting support files.
> 
> It also includes some minor bugfixes and adds Documentation for the
> Python support, which includes a step-by-step example detailing how to
> write a new trace stream processing script using Python.
> 
> Finally, it adds several new scripts, all dealing with aggregation of
> system call trace data.  To make those scripts more user-friendly, it
> adds a couple patches that export some of the syscall metadata, enough
> to allow syscall names rather than raw numbers to be printed in the
> output.


Sorry to answer that late.

This looks very nice! And seeing how you made it easy to plug
new languages, and how easy it is to write trace report scripts,
this looks like a cool new step for the tracing over perf tools.

Focusing on scripts to post-process the tracing will certainly
accelerate the movement in this area.

I've looked at some patches in the set, this looks good at
a first glance. I'll review it in detail and test it, and
then apply/push it if I don't encounter problems.

Thanks a lot!

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