> > On Fri, Aug 21, 2015 at 08:25:24PM +0000, Liang, Kan wrote: > > SNIP > > > > > > > we need global topology information in perf.data and use the mapping > > > from there, we can't use current server info > > > > > > we currently store core_siblings_list and thread_siblings_list, in > > > topology FEATURE, which is probably not enough > > > > > > > core_siblings_list includes the cpu list in the same socket. > > thread_siblings_list includes the cpu list in the same core. > > numa_nodes includes the cpu list for each node. > > > > It looks we have enough data from topology FEATURE. > > hum, haven't hecked deeply.. how will you get core id for cpu? >
from thread_siblings_list. I just noticed that svg_build_topology_map did the similar thing to get topology map for timechart from perf header. > > > > What do you think about the function as below? > > It gets the socket id from env. > > some sort of caching would be nice, I guess we could store those cpumap > objects within perf_session_env Yes it will be stored in perf_session_env. Thanks, Kan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/