[GIT PULL 0/7] perf/urgent fixes

From: Arnaldo Carvalho de Melo
Date: Wed Feb 25 2015 - 16:05:56 EST


Hi Ingo,

Please consider pulling,

- Arnaldo

The following changes since commit 2a6730c8b6e075adf826a89a3e2caa705807afdb:

kprobes/x86: Check for invalid ftrace location in __recover_probed_insn() (2015-02-21 10:33:31 +0100)

are available in the git repository at:

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

for you to fetch changes up to 4861f87cd3d133f03e3b39b6650f4e12f1a9e421:

perf tools: Make sparc64 arch point to sparc (2015-02-25 17:39:17 -0300)

----------------------------------------------------------------
perf/urgent fixes:

Infrastructure:

- pthread_attr_setaffinity_np feature detection build fixes (Adrian Hunter, Josh Boyer)

- Fix probing for PERF_FLAG_FD_CLOEXEC flag (Adrian Hunter)

- Fix order of arguments to memcpy_alloc_mem in 'perf bench' (Bruce Merry)

- Sparc64 and Aarch64 build and segfault fixes (David Ahern)

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

----------------------------------------------------------------
Adrian Hunter (2):
perf tools: Fix pthread_attr_setaffinity_np build error
perf tools: Fix probing for PERF_FLAG_FD_CLOEXEC flag

Bruce Merry (1):
perf bench: Fix order of arguments to memcpy_alloc_mem

David Ahern (3):
perf top: Fix SIGBUS on sparc64
perf symbols: Define EM_AARCH64 for older OSes
perf tools: Make sparc64 arch point to sparc

Josh Boyer (1):
perf tools: Define _GNU_SOURCE on pthread_attr_setaffinity_np feature check

tools/perf/bench/mem-memcpy.c | 4 ++--
tools/perf/config/Makefile.arch | 4 ++++
tools/perf/config/feature-checks/Makefile | 2 +-
.../feature-checks/test-pthread-attr-setaffinity-np.c | 3 ++-
tools/perf/util/cloexec.c | 18 +++++++++++++++---
tools/perf/util/evlist.h | 2 +-
tools/perf/util/symbol-elf.c | 5 +++++
7 files changed, 30 insertions(+), 8 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/