[GIT PULL 0/5] perf/core improvements and fixes

From: Arnaldo Carvalho de Melo
Date: Wed Oct 07 2015 - 18:45:41 EST


Hi Ingo,

Please consider pulling,

- Arnaldo

The following changes since commit 712df65ccb63da08a484bf57c40b250dfd4103a7:

perf/x86/intel/uncore: Fix multi-segment problem of perf_event_intel_uncore (2015-10-06 17:31:51 +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 ae938802443732e77d01f8d5b52b900b9327ff30:

perf python: Support the PERF_RECORD_SWITCH event (2015-10-07 19:41:50 -0300)

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

User visible:

- Adding a field via 'perf report -F' that already is enabled makes
the tool get stuck in a loop, fix it (Jiri Olsa)

Infrastructure:

- Support PERF_RECORD_SWITCH in the python binding (Arnaldo Carvalho de Melo)

- Fix handling read() result using a signed variable, found with Coccinelle
(Andrzej Hajda)

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

----------------------------------------------------------------
Andrzej Hajda (1):
perf tools: Fix handling read result using a signed variable

Arnaldo Carvalho de Melo (1):
perf python: Support the PERF_RECORD_SWITCH event

Jiri Olsa (3):
perf tools: Get rid of superfluos call to reset_dimensions
perf tools: Introduce hpp_dimension__add_output function
perf tools: Use hpp_dimension__add_output to register hpp columns

tools/perf/python/twatch.py | 23 +++++++++++++++---
tools/perf/ui/hist.c | 16 ++++++------
tools/perf/util/event.c | 3 ++-
tools/perf/util/python.c | 59 ++++++++++++++++++++++++++++++++++++++++++---
tools/perf/util/sort.c | 8 ++++--
tools/perf/util/sort.h | 2 ++
6 files changed, 93 insertions(+), 18 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/