From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: "acme@kernel.org" <acme@kernel.org>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"mingo@redhat.com" <mingo@redhat.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"eranian@google.com" <eranian@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 02/10] perf,tools: Support new sort type --socket
Date: Mon, 24 Aug 2015 16:27:53 +0200 [thread overview]
Message-ID: <20150824142753.GB3699@krava.redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077018F21A5@SHSMSX103.ccr.corp.intel.com>
On Mon, Aug 24, 2015 at 02:22:08PM +0000, Liang, Kan wrote:
> >
> > 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.
could you please provide both functions then cpu -> core, cpu -> socket
thanks,
jirka
next prev parent reply other threads:[~2015-08-24 14:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:25 [PATCH RFC 00/10] stat read during perf sampling kan.liang
2015-08-18 9:25 ` [PATCH RFC 01/10] perf,tools: open event on evsel cpus and threads kan.liang
2015-08-20 8:57 ` Jiri Olsa
2015-08-20 17:24 ` Liang, Kan
2015-08-21 7:43 ` Jiri Olsa
2015-08-21 13:24 ` Liang, Kan
2015-08-18 9:25 ` [PATCH RFC 02/10] perf,tools: Support new sort type --socket kan.liang
2015-08-20 9:09 ` Jiri Olsa
2015-08-21 20:25 ` Liang, Kan
2015-08-23 22:00 ` Jiri Olsa
2015-08-24 14:22 ` Liang, Kan
2015-08-24 14:27 ` Jiri Olsa [this message]
2015-08-24 16:47 ` Liang, Kan
2015-08-24 19:30 ` Jiri Olsa
2015-08-27 18:24 ` Jiri Olsa
2015-08-27 18:29 ` Liang, Kan
2015-08-18 9:25 ` [PATCH RFC 03/10] perf,tools: support option --socket kan.liang
2015-08-18 17:36 ` Stephane Eranian
2015-08-20 9:30 ` Jiri Olsa
2015-08-18 9:25 ` [PATCH RFC 04/10] perf,tools: Add 'N' event/group modifier kan.liang
2015-08-18 9:25 ` [PATCH RFC 05/10] perf,tools: Enable statistic read for perf record kan.liang
2015-08-20 9:39 ` Jiri Olsa
2015-08-20 9:41 ` Jiri Olsa
2015-08-18 9:25 ` [PATCH RFC 06/10] perf,tools: New RECORD type PERF_RECORD_STAT_READ kan.liang
2015-08-20 9:49 ` Jiri Olsa
2015-08-18 9:25 ` [PATCH RFC 07/10] perf,tools: record counter statistics during sampling kan.liang
2015-08-18 9:25 ` [PATCH RFC 08/10] perf,tools: option to set stat read interval kan.liang
2015-08-18 9:25 ` [PATCH RFC 09/10] perf,tools: don't validate non-sample event kan.liang
2015-08-18 9:25 ` [PATCH RFC 10/10] perf,tools: Show STAT_READ in perf report kan.liang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150824142753.GB3699@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome