[GIT PULL 0/5] perf/urgent fixes

From: Arnaldo Carvalho de Melo
Date: Thu Feb 13 2014 - 16:17:12 EST


From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>

Hi Ingo,

Please consider pulling,

- Arnaldo

The following changes since commit 0e9f2204cfa6d79abe3e525ddf7c4ab5792cc751:

perf/x86: Fix Userspace RDPMC switch (2014-02-09 13:08:25 +0100)

are available in the git repository at:

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

for you to fetch changes up to 844ae5b46c08dbc7ba695b543c023f9cf3bbf9ff:

perf trace: Fix ioctl 'request' beautifier build problems on !(i386 || x86_64) arches (2014-02-13 17:28:31 -0300)

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

. Handle PERF_RECORD_HEADER_EVENT_TYPE properly. (Jiri Olsa)

. Fix checking for supported events on older kernels in
'perf list' (Vince Weaver)

. Do not add offset twice to uprobe address in
'perf probe' (Masami Hiramatsu)

. Fix perf trace's ioctl 'request' beautifier build problems
on !(i386 || x86_64) arches (Arnaldo Carvalho de Melo)

. Fix 'perf trace' build by adding a fallback definition for
EFD_SEMAPHORE (Ben Hutchings)

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

----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
perf trace: Fix ioctl 'request' beautifier build problems on !(i386 || x86_64) arches

Ben Hutchings (1):
perf trace: Add fallback definition of EFD_SEMAPHORE

Jiri Olsa (1):
perf tools: Handle PERF_RECORD_HEADER_EVENT_TYPE properly

Masami Hiramatsu (1):
perf probe: Do not add offset twice to uprobe address

Vince Weaver (1):
perf list: Fix checking for supported events on older kernels

tools/perf/builtin-trace.c | 22 ++++++++++++++++++++++
tools/perf/util/parse-events.c | 17 +++++++++++++++--
tools/perf/util/probe-event.c | 2 +-
tools/perf/util/session.c | 6 ++++++
4 files changed, 44 insertions(+), 3 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/