linux-kernel - Re: [RFC][PATCH 5/9] perf trace: Add Perl 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] [day] [month] [year] [list]

Message-ID: <20091012060308.GH14995@elte.hu>
Date:	Mon, 12 Oct 2009 08:03:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Tom Zanussi <tzanussi@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org, rostedt@...dmis.org,
	lizf@...fujitsu.com
Subject: Re: [RFC][PATCH 5/9] perf trace: Add Perl scripting support


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> > ad-hoc extensions using separate perf-* scripts are fine of course 
> > and i use that myself. But once a facility is part of core perf it 
> > wants to move into the binary. Especially something as central as 
> > scripting support.
> 
> But I think we may want to have some integrated scripts that can play 
> the role of subcommands when it comes to process particular trace 
> events. Because this is just about reading binary traces and put them 
> in a shape that makes sense wrt to the targeted events.

Maybe - and even in those cases we can still embedd those scripts in the 
binary itself (i.e. we can add a mechanism to embedd it as a string and 
execute it from there). It's not like people are going to edit an 
installed script in a bin/ or libexec/ path.

Same goes for any .xml file should we grow a GUI - etc.

	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/