From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Yicong Yang <yangyicong@huawei.com>,
will@kernel.org, john.g.garry@oracle.com, james.clark@arm.com,
mike.leach@linaro.org, leo.yan@linaro.org, peterz@infradead.org,
mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, jonathan.cameron@huawei.com,
hejunhao3@huawei.com, prime.zeng@hisilicon.com,
yangyicong@hisilicon.com, linuxarm@huawei.com
Subject: Re: [PATCH v2] perf stat: Enable iostat mode for HiSilicon PCIe PMU
Date: Fri, 9 Feb 2024 10:30:59 -0300 [thread overview]
Message-ID: <ZcYpE35VxRClBP_W@x1> (raw)
In-Reply-To: <4688a613-c94a-49b0-9d0f-09173c64082d@arm.com>
On Fri, Feb 09, 2024 at 10:59:04AM +0000, Robin Murphy wrote:
> On 2024-02-08 11:58 pm, Namhyung Kim wrote:
> > On Wed, Feb 7, 2024 at 7:29 PM Yicong Yang <yangyicong@huawei.com> wrote:
> > > From: Yicong Yang <yangyicong@hisilicon.com>
> > > Some HiSilicon platforms provide PCIe PMU devices for monitoring the
> > > throughput and latency of PCIe traffic. With the support of PCIe PMU
> > > we can enable the perf iostat mode.
> > Hmm.. so it only works for HiSilicon. What if users run it on a different
> > platform?
> Same thing as if they run it on an AMD or older Intel platform ;)
> > I think ARM should care about this.
> Arm don't make PCIe root ports, and there is no PMU standardisation between
> all the myriad different implementers and vendors of PCIe IP, so the best
> perf can reasonably do is simply support the particular PMUs that people
> want perf to support.
yeah, that will make perf more useful to more people, which is good.
And it is reusing something we did in the past for a similar mode on
Intel, from what I remember and by looking at:
---------------------------
commit f9ed693e8bc0e7de9eb766a3c7178590e8bb6cd5
Author: Alexander Antonov <alexander.antonov@linux.intel.com>
Date: Mon Apr 19 12:41:46 2021 +0300
perf stat: Enable iostat mode for x86 platforms
This functionality is based on recently introduced sysfs attributes for
Intel® Xeon® Scalable processor family (code name Skylake-SP):
Commit bb42b3d39781d7fc ("perf/x86/intel/uncore: Expose an Uncore unit to IIO PMON mapping")
Mode is intended to provide four I/O performance metrics in MB per each
PCIe root port:
- Inbound Read: I/O devices below root port read from the host memory
- Inbound Write: I/O devices below root port write to the host memory
- Outbound Read: CPU reads from I/O devices below root port
- Outbound Write: CPU writes to I/O devices below root port
Each metric requiries only one uncore event which increments at every 4B
transfer in corresponding direction. The formulas to compute metrics
are generic:
#EventCount * 4B / (1024 * 1024)
---------------------------
And tools/perf/perf-iostat.sh.
Right?
- Arnaldo
_______________________________________________
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:[~2024-02-09 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:25 [PATCH v2] perf stat: Enable iostat mode for HiSilicon PCIe PMU Yicong Yang
2024-02-08 10:46 ` Jonathan Cameron
2024-02-21 8:16 ` Yicong Yang
2024-02-08 23:58 ` Namhyung Kim
2024-02-09 1:08 ` Leo Yan
2024-02-09 10:59 ` Robin Murphy
2024-02-09 13:30 ` Arnaldo Carvalho de Melo [this message]
2024-02-09 13:47 ` Arnaldo Carvalho de Melo
2024-02-21 8:13 ` Yicong Yang
2024-02-09 13:51 ` Leo Yan
2024-02-21 7:19 ` Yicong Yang
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=ZcYpE35VxRClBP_W@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hejunhao3@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.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;
as well as URLs for NNTP newsgroup(s).