|| ||Arnaldo Carvalho de Melo <acme-AT-infradead.org> |
|| ||Borislav Petkov <bp-AT-alien8.de>, Borislav Petkov <bp-AT-amd64.org>,
"tony.luck-AT-intel.com" <tony.luck-AT-intel. |
|| ||Re: [PATCH 08/12] perf: Carve out mmap helpers for general use |
|| ||Wed, 26 Jan 2011 11:13:16 -0200|
|| ||Article, Thread
Em Wed, Jan 26, 2011 at 02:00:02AM +0100, Borislav Petkov escreveu:
> On Mon, Jan 24, 2011 at 10:39:36AM -0200, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jan 24, 2011 at 10:04:10AM +0100, Borislav Petkov escreveu:
> > I'm digressing, but twatch is an example of a simple "daemon" consuming
> > perf events where performance is not much of a problem.
> > And provides a prototyping ground when starting to design perf events
> > consuming daemons :-)
> Yaay, twatch looks almost like a child's play and even my grandma can
> profile her system now :).
> But yeah, I thought about pythonizing the ras thingy too but the
> reasons against it are that we might run on systems which don't have
> python, have some obscure/old version of it or we simply don't want to
> depend on it or any other additional tool for that matter. Generally,
> we want to run with as low overhead as possible when handling hw error
> info and be as self-contained as possible.
Right, that is why I try to have the python abstractions as close as
possible to the abstractions a C program, like your RAS thingy should
I.e. one can go on introducing the kernel interfaces and testing them
using python, where you can, for instance, from the python interpreter
command line, create counters, read its values, i.e. test the kernel
stuff quickly and easily.
Moving to a C version then becomes easy after the testing phase is over
and the kernel bits are set in stone.
to post comments)