[GIT PULL 00/19] perf/core improvements and fixes

From: Arnaldo Carvalho de Melo
Date: Fri Feb 27 2015 - 14:28:40 EST


Hi Ingo,

Please consider pulling,

- Arnaldo

The following changes since commit 0afb1704010f60e7ae85aef0f93fc10f2d99761e:

Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2015-02-26 12:25:20 +0100)

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 fefd2d9619de3bf0bf02a8622e9f445c3d19cc3f:

perf report: Fix branch stack mode cannot be set (2015-02-27 15:52:42 -0300)

----------------------------------------------------------------
perf/core improvements and fixes:

User visible:

- Fix SIGBUS failures due to misaligned accesses in Sparc64 (David Ahern)

- Fix branch stack mode in 'perf report' (He Kuang)

- Fix a 'perf probe' operator precedence bug (He Kuang)

- Fix Support for different binaries with same name in 'perf diff' (Kan Liang)

- Check kprobes blacklist when adding new events via 'perf probe' (Masami Hiramatsu)

- Add --purge FILE to remove all caches of FILE in 'perf buildid-cache' (Masami Hiramatsu)

- Show usage with some incorrect params (Masami Hiramatsu)

- Add new buildid cache if update target is not cached in 'buildid-cache' (Masami Hiramatsu)

- Allow listing events with 'tracepoint' prefix in 'perf list' (Yunlong Song)

- Sort the output of 'perf list' (Yunlong Song)

- Fix bash completion of 'perf --' (Yunlong Song)

Developer Zone:

- Handle strdup() failure path in 'perf probe' (Arnaldo Carvalho de Melo)

- Fix get_real_path to free allocated memory in error path in 'perf probe' (Masami Hiramatsu)

- Use pr_debug instead of verbose && pr_info perf buildid-cache (Masami Hiramatsu)

- Fix building of 'perf data' with some gcc versions due to incorrect array struct
entry (Yunlong Song)

Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>

----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
perf probe: Handle strdup() failure

David Ahern (1):
perf trace: Fix SIGBUS failures due to misaligned accesses

He Kuang (2):
perf probe: Fix a precedence bug
perf report: Fix branch stack mode cannot be set

Kan Liang (1):
perf diff: Support for different binaries

Masami Hiramatsu (6):
perf probe: Check kprobes blacklist when adding new events
perf probe: Fix get_real_path to free allocated memory in error path
perf buildid-cache: Add new buildid cache if update target is not cached
perf buildid-cache: Add --purge FILE to remove all caches of FILE
perf buildid-cache: Use pr_debug instead of verbose && pr_info
perf buildid-cache: Show usage with incorrect params

Yunlong Song (8):
perf data: Fix sentinel setting for data_cmds array
perf list: Sort the output of 'perf list' to view more clearly
perf list: Allow listing events with 'tracepoint' prefix
perf list: Avoid confusion of perf output and the next command prompt
perf tools: Remove the '--(null)' long_name for --list-opts
perf list: Clean up the printing functions of hardware/software events
perf list: Extend raw-dump to certain kind of events
perf tools: Fix the bash completion problem of 'perf --*'

tools/perf/Documentation/perf-buildid-cache.txt | 24 ++-
tools/perf/Documentation/perf-diff.txt | 5 +
tools/perf/Documentation/perf-list.txt | 6 +
tools/perf/builtin-buildid-cache.c | 72 ++++++--
tools/perf/builtin-data.c | 2 +-
tools/perf/builtin-list.c | 27 ++-
tools/perf/builtin-report.c | 2 +-
tools/perf/builtin-trace.c | 36 +++-
tools/perf/perf-completion.sh | 6 +-
tools/perf/perf.c | 28 ++++
tools/perf/util/build-id.c | 105 ++++++++++--
tools/perf/util/build-id.h | 4 +
tools/perf/util/parse-events.c | 210 +++++++++++++++++-------
tools/perf/util/parse-events.h | 11 +-
tools/perf/util/parse-options.c | 5 +-
tools/perf/util/probe-event.c | 117 ++++++++++++-
tools/perf/util/sort.c | 9 +
17 files changed, 542 insertions(+), 127 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/