[RFC 0/5] perf tools: Share map groups within process

From: Jiri Olsa
Date: Fri Mar 14 2014 - 10:58:20 EST


hi,
this patchset moves thread's map_groups to be dynamically
allocated and shared within process threads.

The main benefit would be to be able to look up memory
map from any thread that belongs to the process.

This implementes one of the solution ideas for issue
described by Don in following thread:
http://marc.info/?l=linux-kernel&m=139403876017159&w=2

This patches still has some loose ends, just wanted to hear
opinions for this concept.

thanks,
jirka

Signed-off-by: Jiri Olsa <jolsa@xxxxxxxxxx>
Cc: Don Zickus <dzickus@xxxxxxxxxx>
Cc: Corey Ashford <cjashfor@xxxxxxxxxxxxxxxxxx>
Cc: David Ahern <dsahern@xxxxxxxxx>
Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxxxxx>
Cc: Namhyung Kim <namhyung@xxxxxxxxxx>
Cc: Paul Mackerras <paulus@xxxxxxxxx>
Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
Cc: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
---
Jiri Olsa (5):
perf tests: Add tip/pid mmap automated tests
perf tools: Factor machine__find_thread to take tid argument
perf tools: Allocate thread map_groups dynamicaly
perf tools: Add machine pointer into thread struct
perf tools: Share process map groups within process threads

tools/perf/Makefile.perf | 1 +
tools/perf/arch/x86/tests/dwarf-unwind.c | 2 +-
tools/perf/perf.h | 6 ++
tools/perf/tests/builtin-test.c | 4 ++
tools/perf/tests/dwarf-unwind.c | 2 +-
tools/perf/tests/mmap-events.c | 188 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tools/perf/tests/tests.h | 1 +
tools/perf/ui/stdio/hist.c | 8 ++-
tools/perf/util/event.c | 4 +-
tools/perf/util/machine.c | 21 ++++---
tools/perf/util/machine.h | 3 +-
tools/perf/util/map.h | 3 +-
tools/perf/util/thread.c | 87 ++++++++++++++++++++++++++---
tools/perf/util/thread.h | 15 +++--
14 files changed, 317 insertions(+), 28 deletions(-)
create mode 100644 tools/perf/tests/mmap-events.c
--
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/