lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Oct 2014 18:11:13 -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:
> 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
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ