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:	Wed, 12 Jan 2011 14:30:22 -0200
From:	Arnaldo Carvalho de Melo <acme@...radead.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Kirill Smelkov <kirr@....spb.ru>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Stephane Eranian <eranian@...gle.com>,
	Tom Zanussi <tzanussi@...il.com>
Subject: Re: Q: perf log mode?

Em Wed, Jan 12, 2011 at 04:02:33PM +0100, Peter Zijlstra escreveu:
> On Wed, 2011-01-12 at 17:59 +0300, Kirill Smelkov wrote:
> > 
> > Anyway, maybe something like this could be useful?
> > 
> I guess that would be ok, but I'll leave that to Arnaldo.

It is OK, I'll apply it to my perf/core, for the next merge window.
 
> Also note that Arnaldo is revamping the whole script interface to make
> it possible to open and use the perf fds from the script language itself
> (the only sane way), completely removing the dependency on perf-record.

Yep, I'm librarising the ad-hoc counter creation routines we have in
stat, top and record, factoring the common parts, etc, and creating
'perf test' regression test routines for these new library functions.

After I finish the mmap bits, which should be soon, I'll start work on
having a python binding for these routines and experiment plugging it to
some other projects I worked on.

I'll also work on converting a few of the scripts we have to provide
examples of use of this python binding.

Other bindings and a C library can come later, after we settle on an API
using the python binding as the guinea pig.

Parts of this got into this merge window, for instance, perf stat uses
the perf_evsel api to open and read counters, and perf test has new
routines to stress them, new stuff I'm stashing at the perf/test branch
in:

http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=shortlog;h=refs/heads/perf/test

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ