From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 00/16] perf tools: Intel PT preparation continued
Date: Thu, 23 Oct 2014 18:11:13 -0300 [thread overview]
Message-ID: <20141023211113.GO14687@kernel.org> (raw)
In-Reply-To: <1414061124-26830-1-git-send-email-adrian.hunter@intel.com>
Em Thu, Oct 23, 2014 at 01:45:08PM +0300, Adrian Hunter escreveu:
> Hi
>
> Here are the remaining Intel PT preparation patches. They are
> all patches that have been posted before, although "perf tools:
> Do not attempt to run perf-read-vdso32 if it wasn't built" wasn't
> sent as a separate email.
>
> With regard to "32-bit compatibility VDSOs", you may recall that
> Ingo had a problem getting "sh: perf-read-vdso32: command not found".
> That message is inevitable when using popen to run perf-read-vdso32
> and perf-read-vdso32 cannot be found. At least with the patch
> "perf tools: Do not attempt to run perf-read-vdso32 if it wasn't built"
> one reason for the message is eliminated.
The above patches I will try to process, look ok but since they are at
the end of the patch kit, it conflicts if I don't process the ones at
the start of the patchkit, which I am still not confortable merging.
- Arnaldo
> It would be nice to target 3.19 for Intel PT, but there are still the
> real patches of which there are about 48.
>
>
> Adrian Hunter (16):
> perf tools: Add id index
> perf pmu: Let pmu's with no events show up on perf list
> perf session: Add perf_session__deliver_synth_event()
> perf tools: Add a thread stack for synthesizing call chains
> 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: Enhance the thread stack to output call/return data
> 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'
> 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
>
> tools/perf/Makefile.perf | 42 +-
> tools/perf/builtin-inject.c | 1 +
> tools/perf/config/Makefile | 29 +-
> tools/perf/config/Makefile.arch | 8 +
> tools/perf/config/feature-checks/Makefile | 10 +-
> tools/perf/config/feature-checks/test-compile.c | 4 +
> tools/perf/perf-read-vdso.c | 34 +
> .../scripts/python/bin/export-to-postgresql-record | 8 +
> .../scripts/python/bin/export-to-postgresql-report | 29 +
> tools/perf/scripts/python/export-to-postgresql.py | 444 +++++++++++++
> tools/perf/util/comm.h | 1 +
> tools/perf/util/db-export.c | 426 +++++++++++++
> tools/perf/util/db-export.h | 107 ++++
> tools/perf/util/dso.h | 1 +
> tools/perf/util/event.c | 1 +
> tools/perf/util/event.h | 41 ++
> tools/perf/util/evlist.c | 26 +-
> tools/perf/util/evsel.h | 4 +
> tools/perf/util/find-vdso-map.c | 30 +
> tools/perf/util/machine.h | 1 +
> tools/perf/util/pmu.c | 13 +-
> tools/perf/util/pmu.h | 1 +
> .../util/scripting-engines/trace-event-python.c | 395 +++++++++++-
> tools/perf/util/session.c | 136 ++++
> tools/perf/util/session.h | 15 +
> tools/perf/util/symbol.h | 1 +
> tools/perf/util/thread-stack.c | 690 +++++++++++++++++++++
> tools/perf/util/thread-stack.h | 79 +++
> tools/perf/util/thread.c | 3 +
> tools/perf/util/thread.h | 4 +
> tools/perf/util/tool.h | 3 +-
> tools/perf/util/vdso.c | 217 ++++++-
> tools/perf/util/vdso.h | 4 +-
> 33 files changed, 2760 insertions(+), 48 deletions(-)
> create mode 100644 tools/perf/config/feature-checks/test-compile.c
> create mode 100644 tools/perf/perf-read-vdso.c
> create mode 100644 tools/perf/scripts/python/bin/export-to-postgresql-record
> create mode 100644 tools/perf/scripts/python/bin/export-to-postgresql-report
> create mode 100644 tools/perf/scripts/python/export-to-postgresql.py
> create mode 100644 tools/perf/util/db-export.c
> create mode 100644 tools/perf/util/db-export.h
> create mode 100644 tools/perf/util/find-vdso-map.c
> create mode 100644 tools/perf/util/thread-stack.c
> create mode 100644 tools/perf/util/thread-stack.h
>
>
> Regards
> Adrian
next prev parent reply other threads:[~2014-10-23 21:11 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 10:45 [PATCH 00/16] perf tools: Intel PT preparation continued Adrian Hunter
2014-10-23 10:45 ` [PATCH 01/16] perf tools: Add id index Adrian Hunter
2014-10-23 21:08 ` Arnaldo Carvalho de Melo
2014-10-24 5:10 ` Namhyung Kim
2014-10-24 7:25 ` Adrian Hunter
2014-10-29 8:55 ` Jiri Olsa
2014-10-23 10:45 ` [PATCH 02/16] perf pmu: Let pmu's with no events show up on perf list Adrian Hunter
2014-10-24 5:15 ` Namhyung Kim
2014-10-24 12:57 ` Arnaldo Carvalho de Melo
2014-10-24 13:03 ` Arnaldo Carvalho de Melo
2014-10-24 13:21 ` Arnaldo Carvalho de Melo
2014-10-24 14:36 ` Adrian Hunter
2014-10-24 14:38 ` Adrian Hunter
2014-10-24 14:45 ` Arnaldo Carvalho de Melo
2014-10-24 15:35 ` Arnaldo Carvalho de Melo
2014-10-30 6:45 ` [tip:perf/core] perf pmu: Let pmu' s " tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 03/16] perf session: Add perf_session__deliver_synth_event() Adrian Hunter
2014-10-24 5:22 ` Namhyung Kim
2014-10-24 10:41 ` Adrian Hunter
2014-10-23 10:45 ` [PATCH 04/16] perf tools: Add a thread stack for synthesizing call chains Adrian Hunter
2014-10-23 20:51 ` Arnaldo Carvalho de Melo
2014-10-24 8:47 ` Adrian Hunter
2014-10-24 5:41 ` Namhyung Kim
2014-10-29 9:03 ` Jiri Olsa
2014-10-29 9:07 ` Jiri Olsa
2014-10-23 10:45 ` [PATCH 05/16] perf tools: Add facility to export data in database-friendly way Adrian Hunter
2014-10-23 21:42 ` Arnaldo Carvalho de Melo
2014-10-24 6:02 ` Namhyung Kim
2014-10-24 8:11 ` Adrian Hunter
2014-10-24 10:47 ` Adrian Hunter
2014-10-24 12:26 ` Namhyung Kim
2014-10-24 13:13 ` Adrian Hunter
2014-10-24 14:40 ` Arnaldo Carvalho de Melo
2014-10-24 14:41 ` Arnaldo Carvalho de Melo
2014-10-30 6:46 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 06/16] perf tools: Extend Python script interface to export data in a " Adrian Hunter
2014-10-30 6:47 ` [tip:perf/core] perf scripting python: Extend " tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 07/16] perf tools: Add Python script to export to postgresql Adrian Hunter
2014-10-30 6:47 ` [tip:perf/core] perf script: " tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 08/16] perf tools: Add branch type to db export Adrian Hunter
2014-10-23 10:45 ` [PATCH 09/16] perf tools: Add branch_type and in_tx to Python export Adrian Hunter
2014-10-23 10:45 ` [PATCH 10/16] perf tools: Enhance the thread stack to output call/return data Adrian Hunter
2014-10-29 13:23 ` Jiri Olsa
2014-10-29 14:02 ` Arnaldo Carvalho de Melo
2014-10-23 10:45 ` [PATCH 11/16] perf tools: Add call information to the database export API Adrian Hunter
2014-10-23 10:45 ` [PATCH 12/16] perf tools: Add call information to Python export Adrian Hunter
2014-10-23 10:45 ` [PATCH 13/16] perf tools: Defer export of comms that were not 'set' Adrian Hunter
2014-10-23 10:45 ` [PATCH 14/16] perf tools: Build programs to copy 32-bit compatibility VDSOs Adrian Hunter
2014-10-30 6:45 ` [tip:perf/core] perf tools: Build programs to copy 32-bit compatibility tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 15/16] perf tools: Add support for 32-bit compatibility VDSOs Adrian Hunter
2014-10-30 6:45 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-23 10:45 ` [PATCH 16/16] perf tools: Do not attempt to run perf-read-vdso32 if it wasn't built Adrian Hunter
2014-10-30 6:46 ` [tip:perf/core] " tip-bot for Adrian Hunter
2014-10-23 21:11 ` Arnaldo Carvalho de Melo [this message]
2014-10-23 23:43 ` [PATCH 00/16] perf tools: Intel PT preparation continued Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141023211113.GO14687@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).