[RFC 00/13] perf_env/CPU socket reorg/fixes

From: Arnaldo Carvalho de Melo
Date: Wed Sep 09 2015 - 15:53:03 EST


Hi,

Please take a look at these changes to fix the problems reported by
Wang Nan wrt accesses to the cpu_topology_map information.

The fixes are present on these following two csets:

perf event: Use machine->env to find the cpu -> socket mapping
perf report: Do not blindly use env->cpu[al.cpu].socket_id

The rest are fixes made while working on this, infrastructure to enable
the fixes, reverts for things that ended up not being necessary and some
cleanups.

It is available at:

git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/env

Please let me know if I can have your Acked-by, Tested-by or
Reviewed-by.

- Arnaldo

Arnaldo Carvalho de Melo (13):
perf env: Move perf_env out of header.h and session.c into separate object
perf env: Rename some leftovers from rename to perf_env
perf env: Adopt perf_header__set_cmdline
perf env: Introduce read_cpu_topology_map() method
perf sort: Set flag stating if the "socket" key is being used
perf top: Cache the cpu topology info when "-s socket" is used
perf hists browser: Fixup the "cpu" column width calculation
perf machine: Add pointer to sample's environment
perf event: Use machine->env to find the cpu -> socket mapping
perf report: Do not blindly use env->cpu[al.cpu].socket_id
Revert "perf evsel: Add a backpointer to the evlist a evsel is in"
perf evsel: Remove forward declaration of 'struct perf_evlist'
Revert "perf evlist: Add backpointer for perf_env to evlist"
--
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/