[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111125104535.GN15738@erda.amd.com>
Date: Fri, 25 Nov 2011 11:45:35 +0100
From: Robert Richter <robert.richter@....com>
To: Arnaldo Carvalho de Melo <acme@...hat.com>
CC: <mingo@...hat.com>, <eranian@...gle.com>,
<linux-kernel@...r.kernel.org>, <fweisbec@...il.com>,
<efault@....de>, <peterz@...radead.org>
Subject: Re: libperf interface stability
On 24.11.11 16:10:52, Arnaldo Carvalho de Melo wrote:
> Em Thu, Nov 24, 2011 at 05:28:45PM +0100, Robert Richter escreveu:
> > It would be good to have a well defined, stable libperf interface for
> > tools other than perf.
>
> Agreed, an effort in this direction was the perf python binding, that so
> far includes only:
>
> tools/perf/util/setup.py
>
> sources = ['util/python.c', 'util/ctype.c', 'util/evlist.c',
> 'util/evsel.c', 'util/cpumap.c', 'util/thread_map.c',
> 'util/util.c', 'util/xyarray.c', 'util/cgroup.c',
> 'util/debugfs.c'],
>
> You need https://github.com/acmel/linux/commits/perf/urgent to build it
> tho, it has a fix for that:
>
> In the end it generates a ~/build/perf/python/perf.so file (I use make
> -C tools/perf O=/home/acme/build/perf) that has all that is needed for
> simple tools like tools/perf/python/twatch.py.
>
> I think of it as a precursor for a shared library for use with C and I
> have been working on untangling references such as the symbol_conf one
> you mentioned and making the 'perf_evlist' and 'perf_evsel' classes the
> main way to work with libperf.
Thanks Arnaldo, will then take this as a base to start with.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
--
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