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

Message-Id: <1254974493.6841.17.camel@tropicana>
Date:	Wed, 07 Oct 2009 23:01:33 -0500
From:	Tom Zanussi <tzanussi@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	fweisbec@...il.com, rostedt@...dmis.org, lizf@...fujitsu.com
Subject: Re: [RFC][PATCH 5/9] perf trace: Add Perl scripting support

On Wed, 2009-10-07 at 10:13 -0400, Christoph Hellwig wrote:
> On Tue, Oct 06, 2009 at 11:09:25PM -0500, Tom Zanussi wrote:
> > > I think we also want to have a 'perf -s *' kind of thing to get a list 
> > > of all available language modules.
> > > 
> > 
> > I knew somebody would point that out (and suggest a better way ;-)  That
> > all makes sense - I'll make these changes in the next version.
> 
> I'm a bit worried about linking two million scripting language into the
> main perf binary.  Can't we just have seaprate perlperf / pythonperf,
> rubyperf, awkperf binaries that only contain the scripting support?
> 

Yeah, that's a good point.  Maybe support for each language should be
implemented as shared library 'plugins', where the right one gets loaded
dynamically using dlopen/dlsym based on the type of script invoked or
command-line option used.  I'll try something like that for the next
version.

Tom

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