[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141023234352.GS14687@kernel.org>
Date: Thu, 23 Oct 2014 20:43:52 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 00/16] perf tools: Intel PT preparation continued
Em Thu, Oct 23, 2014 at 01:45:08PM +0300, Adrian Hunter escreveu:
> Adrian Hunter (16):
Applied these, will test those and put in my next pull req to Ingo:
> perf pmu: Let pmu's with no events show up on perf list
> perf tools: Build programs to copy 32-bit compatibility VDSOs
> perf tools: Add support for 32-bit compatibility VDSOs
> perf tools: Do not attempt to run perf-read-vdso32 if it wasn't built
The next two are related, made questions about the first:
> perf tools: Add id index
> perf session: Add perf_session__deliver_synth_event()
Made some questions about these two as well:
> perf tools: Add a thread stack for synthesizing call chains
> perf tools: Enhance the thread stack to output call/return data
These all are about the db_export, if time permits tomorrow I'll try to
do what I suggested and post a patch for you to see, i.e. basically the
first one is the one with the questions.
> perf tools: Add facility to export data in database-friendly way
> perf tools: Extend Python script interface to export data in a database-friendly way
> perf tools: Add Python script to export to postgresql
> perf tools: Add branch type to db export
> perf tools: Add branch_type and in_tx to Python export
> perf tools: Add call information to the database export API
> perf tools: Add call information to Python export
> perf tools: Defer export of comms that were not 'set'
- 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