From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com, ying.huang@intel.com
Subject: Re: [PATCH v6] perf stat: Fix wrong skipping for per-die aggregation
Date: Thu, 14 Jan 2021 20:00:32 +0100 [thread overview]
Message-ID: <20210114190032.GC1416940@krava> (raw)
In-Reply-To: <20210114012755.1106-1-yao.jin@linux.intel.com>
On Thu, Jan 14, 2021 at 09:27:55AM +0800, Jin Yao wrote:
SNIP
> 2.003776312 S1-D0 1 855616 Bytes llc_misses.mem_read
> 2.003776312 S1-D1 1 949376 Bytes llc_misses.mem_read
> 3.006512788 S0-D0 1 1338880 Bytes llc_misses.mem_read
> 3.006512788 S0-D1 1 920064 Bytes llc_misses.mem_read
> 3.006512788 S1-D0 1 877184 Bytes llc_misses.mem_read
> 3.006512788 S1-D1 1 1020736 Bytes llc_misses.mem_read
> 4.008895291 S0-D0 1 926592 Bytes llc_misses.mem_read
> 4.008895291 S0-D1 1 906368 Bytes llc_misses.mem_read
> 4.008895291 S1-D0 1 892224 Bytes llc_misses.mem_read
> 4.008895291 S1-D1 1 987712 Bytes llc_misses.mem_read
> 5.001590993 S0-D0 1 962624 Bytes llc_misses.mem_read
> 5.001590993 S0-D1 1 912512 Bytes llc_misses.mem_read
> 5.001590993 S1-D0 1 891200 Bytes llc_misses.mem_read
> 5.001590993 S1-D1 1 978432 Bytes llc_misses.mem_read
>
> On no-die system, die_id is 0, actually it's hashmap(socket,0), original behavior
> is not changed.
>
> Reported-by: Huang Ying <ying.huang@intel.com>
> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> ---
> v6:
> Fix the perf test python failure by adding hashmap.c to python-ext-sources.
>
> root@kbl-ppc:~# ./perf test python
> 19: 'import perf' in python : Ok
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
next prev parent reply other threads:[~2021-01-14 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 1:27 [PATCH v6] perf stat: Fix wrong skipping for per-die aggregation Jin Yao
2021-01-14 19:00 ` Jiri Olsa [this message]
2021-01-15 20:28 ` Arnaldo Carvalho de Melo
2021-01-15 20:31 ` Arnaldo Carvalho de Melo
2021-01-18 4:16 ` Jin, Yao
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=20210114190032.GC1416940@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.intel.com \
--cc=ying.huang@intel.com \
/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