linux-kernel - Re: [GIT PULL 0/7] perf/core refactorings and improvements

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:	Wed, 27 May 2015 21:27:25 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Adrian Hunter <adrian.hunter@...el.com>,
	Andi Kleen <ak@...ux.intel.com>, Borislav Petkov <bp@...e.de>,
	David Ahern <dsahern@...il.com>,
	Don Zickus <dzickus@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Michael Petlan <mpetlan@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [GIT PULL 0/7] perf/core refactorings and improvements

Em Wed, May 27, 2015 at 09:05:27PM -0300, Arnaldo Carvalho de Melo escreveu:
> Hi Ingo,
> 
> 	Please consider applying,

Sorry, missed the git-request-pull part, ouch, here it is:

The following changes since commit 6632c4b4e96c668e19173fa17f2c58c60490bac3:

  Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2015-05-27 18:42:36 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo

for you to fetch changes up to f00898f4e20b286877b8d6d96d6e404661fd7985:

  perf tools: Move branch option parsing to own file (2015-05-27 21:02:17 -0300)

----------------------------------------------------------------
perf/core refactorings and improvements:

User visible:

- Add hint for 'Too many events are opened.' error message (Jiri Olsa)

Infrastructure:

- Protect accesses to map rbtrees with a lock and refcount struct map,
  reducing memory usage as maps not used get freed. The 'dso' struct is
  next in line. (Arnaldo Carvalho de Melo)

- Annotation and branch related option parsing refactorings to
  share code with upcoming patches (Andi Kleen)

Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com>

----------------------------------------------------------------
Andi Kleen (2):
      perf annotation: Add symbol__get_annotation
      perf tools: Move branch option parsing to own file

Arnaldo Carvalho de Melo (4):
      perf tools: Introduce struct maps
      perf tools: Protect accesses the map rbtrees with a rw lock
      perf tools: Check if a map is still in use when deleting it
      perf tools: Reference count struct map

Jiri Olsa (1):
      perf tools: Add hint for 'Too many events are opened.' error message

 tools/perf/builtin-annotate.c          |   4 +
 tools/perf/builtin-record.c            |  89 +--------------
 tools/perf/tests/vmlinux-kallsyms.c    |   2 +-
 tools/perf/util/Build                  |   1 +
 tools/perf/util/annotate.c             |  21 ++--
 tools/perf/util/event.c                |   2 +-
 tools/perf/util/evsel.c                |   4 +-
 tools/perf/util/machine.c              |   3 +-
 tools/perf/util/map.c                  | 190 +++++++++++++++++++++++----------
 tools/perf/util/map.h                  |  29 +++--
 tools/perf/util/parse-branch-options.c |  93 ++++++++++++++++
 tools/perf/util/parse-branch-options.h |   5 +
 tools/perf/util/probe-event.c          |   8 +-
 tools/perf/util/symbol-elf.c           |   2 +
 tools/perf/util/symbol.c               |  36 +++++--
 15 files changed, 315 insertions(+), 174 deletions(-)
 create mode 100644 tools/perf/util/parse-branch-options.c
 create mode 100644 tools/perf/util/parse-branch-options.h
--
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/