[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130504081017.GC14614@gmail.com>
Date: Sat, 4 May 2013 10:10:17 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Stephane Eranian <eranian@...gle.com>,
Jiri Olsa <jolsa@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Namhyung Kim <namhyung@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/8] perf tools: Add '.' as part of the event 'name' token
* Peter Zijlstra <peterz@...radead.org> wrote:
> > I meant to add that I think it would be more productive if we (you and I) were
> > to work on the library to extend it with external text-based event tables that
> > could be used by perf either directly or thru the libpfm4 interface.
>
> That would be very useful indeed.. I think we talked about this before.
> Also wasn't there some vendor support for this idea as well?
>
> I think we want a format that is relatively simple to parse and human
> readable (which excludes XML on both counts ;-).
>
> The main objection of using libpfm4 has always been that its primarily
> something else. It also does the event listing thing, but that's only a
> small part of it.
>
> But if we can split out that part and use it in both projects that would
> be best I think.
If that libpfm reference library moved to tools/lib/ like
tools/lib/traceevents/ then that would be a nice, useful solution indeed.
Thanks,
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/
Powered by blists - more mailing lists