[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150910091906.GA3854@krava.brq.redhat.com>
Date: Thu, 10 Sep 2015 11:19:06 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Kan Liang <kan.liang@...el.com>, Ingo Molnar <mingo@...nel.org>,
linux-kernel@...r.kernel.org,
Adrian Hunter <adrian.hunter@...el.com>,
Borislav Petkov <bp@...e.de>, David Ahern <dsahern@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Stephane Eranian <eranian@...gle.com>,
Wang Nan <wangnan0@...wei.com>
Subject: Re: [RFC 00/13] perf_env/CPU socket reorg/fixes
On Wed, Sep 09, 2015 at 04:50:12PM -0300, Arnaldo Carvalho de Melo wrote:
> 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.
perf_env holds the data for perf.data session.. is the plan to keep
it like this, or it's to be used in some other way? Moving it out of
session/header real suggest that.. just asking ;-)
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists