From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Al Grant <al.grant@foss.arm.com>, Jiri Olsa <jolsa@kernel.org>,
Joe Mario <jmario@redhat.com>
Cc: David Ahern <dsahern@gmail.com>, Don Zickus <dzickus@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, andi.kleen@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf c2c report: count remote loads correctly
Date: Tue, 1 Sep 2020 14:28:23 -0300 [thread overview]
Message-ID: <20200901172823.GF1424523@kernel.org> (raw)
In-Reply-To: <6282053a-d813-8638-531d-56e852d582a2@foss.arm.com>
Em Thu, Aug 20, 2020 at 02:48:58PM +0100, Al Grant escreveu:
> "perf c2c report" can show load counts for cache lines, which don't match
> the actual number of load samples, e.g. as displayed by "perf script". This
> is specific to "Remote Any cache hit" loads. Firstly, these loads are
> counted twice, because if the "remote" flag is set, rmt_dram is always
> incremented, and then rmt_hitm or rmt_hit may also be incremented. These are
> then totalled in the overall load count, causing double-counting. "Remote
> Any cache hit" should not increment rmt_dram. Instead, use LVLNUM to
> discriminate between remote cache and remote DRAM. Also, non-HITM loads to
> remote cache are not being counted as hits (the last column in the cache
> line report is zero), when the SNOOP field is unset. This causes
> under-reporting of the load count. The code currently only increments
> counters if the SNOOP field is set to either HIT or HITM. Instead, for
> access to remote cache (as indicated by LVLNUM), increment rmt_hitm if
> SNOOP=HITM, increment rmt_hit otherwise.
Hi Joe, Jiri, can you please take a look and provide your Acked-by or
better, Reviewed-by?
- Arnaldo
> From: Al Grant <al.grant@arm.com>
Al, please provide Signed-off-by: lines for code your write,
Thanks,
- Arnaldo
> tools/perf/util/mem-events.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c
> index ea0af0bc4314..c6bb86fd4330 100644
> --- a/tools/perf/util/mem-events.c
> +++ b/tools/perf/util/mem-events.c
> @@ -332,11 +332,13 @@ int c2c_decode_stats(struct c2c_stats *stats, struct
> mem_info *mi)
> u64 lvl = data_src->mem_lvl;
> u64 snoop = data_src->mem_snoop;
> u64 lock = data_src->mem_lock;
> + u64 lvlnum = data_src->mem_lvl_num;
> /*
> * Skylake might report unknown remote level via this
> * bit, consider it when evaluating remote HITMs.
> */
> bool mrem = data_src->mem_remote;
> + bool mmem = (lvlnum == PERF_MEM_LVLNUM_RAM || lvlnum ==
> PERF_MEM_LVLNUM_PMEM);
> int err = 0;
>
> #define HITM_INC(__f) \
> @@ -383,7 +385,7 @@ do { \
>
> if ((lvl & P(LVL, REM_RAM1)) ||
> (lvl & P(LVL, REM_RAM2)) ||
> - mrem) {
> + (mrem && mmem)) {
> stats->rmt_dram++;
> if (snoop & P(SNOOP, HIT))
> stats->ld_shared++;
> @@ -394,11 +396,11 @@ do { \
>
> if ((lvl & P(LVL, REM_CCE1)) ||
> (lvl & P(LVL, REM_CCE2)) ||
> - mrem) {
> - if (snoop & P(SNOOP, HIT))
> - stats->rmt_hit++;
> - else if (snoop & P(SNOOP, HITM))
> + (mrem && !mmem)) {
> + if (snoop & P(SNOOP, HITM))
> HITM_INC(rmt_hitm);
> + else
> + stats->rmt_hit++;
> }
>
> if ((lvl & P(LVL, MISS)))
--
- Arnaldo
next parent reply other threads:[~2020-09-01 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6282053a-d813-8638-531d-56e852d582a2@foss.arm.com>
2020-09-01 17:28 ` Arnaldo Carvalho de Melo [this message]
[not found] ` <20200901201717.GA656443@krava>
[not found] ` <20200901204614.GC656443@krava>
[not found] ` <be482330-5532-6c34-ed0a-1c6f79e365fc@redhat.com>
[not found] ` <0ffdeb34-6fa7-380e-3183-8ce1022ed21c@foss.arm.com>
2020-09-02 13:47 ` [PATCH] perf c2c report: count remote loads correctly Arnaldo Carvalho de Melo
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=20200901172823.GF1424523@kernel.org \
--to=acme@kernel.org \
--cc=al.grant@foss.arm.com \
--cc=andi.kleen@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.