From: John Garry <john.g.garry@oracle.com>
To: Jing Zhang <renyu.zj@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Andrew Kilroy <andrew.kilroy@arm.com>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Zhuo Song <zhuo.song@linux.alibaba.com>
Subject: Re: [External] : [RFC PATCH v2 1/6] perf vendor events arm64: Add topdown L1 metrics for neoverse-n2
Date: Mon, 14 Nov 2022 12:59:30 +0000 [thread overview]
Message-ID: <590ff032-d271-48ee-a4d8-141cc070c335@oracle.com> (raw)
In-Reply-To: <1668411720-3581-2-git-send-email-renyu.zj@linux.alibaba.com>
On 14/11/2022 07:41, Jing Zhang wrote:
> The calculation formula of topdown L1 is from the document:
> https://urldefense.com/v3/__https://documentation-service.arm.com/static/60250c7395978b529036da86?token=__;!!ACWV5N9M2RV99hQ!Ll-Jgvfs0LitTCU-hC6i6BKBVJfhke-pbQq2VoO-gmuSAcglQ3ZqMVMd2r0An_5a3ZDPYmn8zXuCrpUbehwnLHplVQ$
So since this is a from "standard" document, did you consider putting
these as an arch std event? I think arch std events would work for
metrics, like they do for regular events.
>
> However, due to the wrong count of stall_slot and stall_slot_frontend
> in neoverse-n2, the real stall_slot and real stall_slot_frontend need
> to subtract cpu_cycles, so when calculating the topdownL1 metrics,
> stall_slot and stall_slot_frontend are corrected.
Is there a reference to this? It would be indeed useful to pass a link
to the n2 doc as these metrics are not part of the arm64 arm. At least I
assume that they are not there.
>
> Since neoverse-n2 does not yet support topdown L2, metricgroups such
> as Cache, TLB, Branch, InstructionsMix, and PEutilization will be
> added to further analysis of performance bottlenecks in the following
> patches.
>
Thanks,
John
WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.g.garry@oracle.com>
To: Jing Zhang <renyu.zj@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Andrew Kilroy <andrew.kilroy@arm.com>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Zhuo Song <zhuo.song@linux.alibaba.com>
Subject: Re: [External] : [RFC PATCH v2 1/6] perf vendor events arm64: Add topdown L1 metrics for neoverse-n2
Date: Mon, 14 Nov 2022 12:59:30 +0000 [thread overview]
Message-ID: <590ff032-d271-48ee-a4d8-141cc070c335@oracle.com> (raw)
In-Reply-To: <1668411720-3581-2-git-send-email-renyu.zj@linux.alibaba.com>
On 14/11/2022 07:41, Jing Zhang wrote:
> The calculation formula of topdown L1 is from the document:
> https://urldefense.com/v3/__https://documentation-service.arm.com/static/60250c7395978b529036da86?token=__;!!ACWV5N9M2RV99hQ!Ll-Jgvfs0LitTCU-hC6i6BKBVJfhke-pbQq2VoO-gmuSAcglQ3ZqMVMd2r0An_5a3ZDPYmn8zXuCrpUbehwnLHplVQ$
So since this is a from "standard" document, did you consider putting
these as an arch std event? I think arch std events would work for
metrics, like they do for regular events.
>
> However, due to the wrong count of stall_slot and stall_slot_frontend
> in neoverse-n2, the real stall_slot and real stall_slot_frontend need
> to subtract cpu_cycles, so when calculating the topdownL1 metrics,
> stall_slot and stall_slot_frontend are corrected.
Is there a reference to this? It would be indeed useful to pass a link
to the n2 doc as these metrics are not part of the arm64 arm. At least I
assume that they are not there.
>
> Since neoverse-n2 does not yet support topdown L2, metricgroups such
> as Cache, TLB, Branch, InstructionsMix, and PEutilization will be
> added to further analysis of performance bottlenecks in the following
> patches.
>
Thanks,
John
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-14 13:01 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:11 [PATCH RFC 0/6] Add metrics for neoverse-n2 Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 1/6] perf vendor events arm64: Add topdown L1 " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 2/6] perf vendor events arm64: Add TLB " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 3/6] perf vendor events arm64: Add cache " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 4/6] perf vendor events arm64: Add branch " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 5/6] perf vendor events arm64: Add PE utilization " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-10-31 11:11 ` [PATCH RFC 6/6] perf vendor events arm64: Add instruction mix " Jing Zhang
2022-10-31 11:11 ` Jing Zhang
2022-11-14 7:41 ` [RFC PATCH v2 0/6] Add " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 1/6] perf vendor events arm64: Add topdown L1 " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 2/6] perf vendor events arm64: Add TLB " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 3/6] perf vendor events arm64: Add cache " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 4/6] perf vendor events arm64: Add branch " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 5/6] perf vendor events arm64: Add PE utilization " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-30 18:58 ` Ian Rogers
2022-11-30 18:58 ` Ian Rogers
2022-12-01 11:08 ` Jing Zhang
2022-12-01 11:08 ` Jing Zhang
2022-12-02 20:05 ` Ian Rogers
2022-12-02 20:05 ` Ian Rogers
2022-12-04 7:10 ` Jing Zhang
2022-12-04 7:10 ` Jing Zhang
2022-11-24 17:14 ` [PATCH v3 6/6] perf vendor events arm64: Add instruction mix " Jing Zhang
2022-11-24 17:14 ` Jing Zhang
2022-11-14 7:41 ` [RFC PATCH v2 1/6] perf vendor events arm64: Add topdown L1 " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-14 12:59 ` John Garry [this message]
2022-11-14 12:59 ` [External] : " John Garry
2022-11-15 8:43 ` Jing Zhang
2022-11-15 8:43 ` Jing Zhang
2022-11-15 11:19 ` John Garry
2022-11-15 11:19 ` John Garry
2022-11-21 9:53 ` Jing Zhang
2022-11-21 9:53 ` Jing Zhang
2022-11-21 10:22 ` John Garry
2022-11-21 10:22 ` John Garry
2022-11-21 15:17 ` Jing Zhang
2022-11-21 15:17 ` Jing Zhang
2022-11-21 17:55 ` John Garry
2022-11-21 17:55 ` John Garry
2022-11-22 9:24 ` Jing Zhang
2022-11-22 9:24 ` Jing Zhang
2022-11-22 14:00 ` James Clark
2022-11-22 14:00 ` James Clark
2022-11-22 15:41 ` Jing Zhang
2022-11-22 15:41 ` Jing Zhang
2022-11-23 14:26 ` James Clark
2022-11-23 14:26 ` James Clark
2022-11-24 16:32 ` Jing Zhang
2022-11-24 16:32 ` Jing Zhang
2022-11-24 16:51 ` James Clark
2022-11-24 16:51 ` James Clark
2022-11-14 7:41 ` [RFC PATCH v2 2/6] perf vendor events arm64: Add TLB " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-14 7:41 ` [RFC PATCH v2 3/6] perf vendor events arm64: Add cache " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-14 8:35 ` Xing Zhengjun
2022-11-14 8:35 ` Xing Zhengjun
2022-11-15 6:28 ` Jing Zhang
2022-11-15 6:28 ` Jing Zhang
2022-11-14 7:41 ` [RFC PATCH v2 4/6] perf vendor events arm64: Add branch " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-14 7:41 ` [RFC PATCH v2 5/6] perf vendor events arm64: Add PE utilization " Jing Zhang
2022-11-14 7:41 ` Jing Zhang
2022-11-14 7:42 ` [RFC PATCH v2 6/6] perf vendor events arm64: Add instruction mix " Jing Zhang
2022-11-14 7:42 ` Jing Zhang
2022-11-16 11:19 ` [PATCH RFC 0/6] Add " James Clark
2022-11-16 11:19 ` James Clark
2022-11-16 15:26 ` Jing Zhang
2022-11-16 15:26 ` Jing Zhang
2022-11-21 11:51 ` James Clark
2022-11-21 11:51 ` James Clark
2022-11-22 7:11 ` Jing Zhang
2022-11-22 7:11 ` Jing Zhang
2022-11-22 11:53 ` James Clark
2022-11-22 11:53 ` James Clark
2022-11-19 3:30 ` Jing Zhang
2022-11-19 3:30 ` Jing Zhang
[not found] ` <CAP-5=fW+Z_Tc3BfK1bRKUeKWfxtPfoZXL9D2BhcU1SzNOruSsg@mail.gmail.com>
2022-11-20 3:49 ` Jing Zhang
2022-11-20 3:49 ` Jing Zhang
2022-11-21 11:55 ` James Clark
2022-11-21 11:55 ` James Clark
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=590ff032-d271-48ee-a4d8-141cc070c335@oracle.com \
--to=john.g.garry@oracle.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.kilroy@arm.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.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 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.