From: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>
To: Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
Ley Foon Tan <leyfoon.tan@starfivetech.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v6 0/4] StarFive's StarLink PMU Support
Date: Mon, 29 Jan 2024 17:51:37 +0800 [thread overview]
Message-ID: <20240129095141.3262366-1-jisheng.teoh@starfivetech.com> (raw)
Changes since v5:
- Add entry to MAINTAINERS and mark the driver as "Maintained".
Changes since v4:
- Add Reviewed-by tag from Conor to dt-bindings.
- Add Documentation/admin-guide/perf/starfive_starlink_pmu.rst.
- Rework starfive_starlink_pmu.c based on Jonathan's comment.
- Use <linux/mod_devicetable.h> in place of <linux/of_device.h>.
- Prefix CYCLES to STARLINK_CYCLES.
- Fixup error handling, remove unnecessary comma after NULL and comments.
Changes since v3:
- Change dt-bindings filename along with the compatible field to
"starfive,jh8100-starlink-pmu" with SOC specific naming
convention.
- Drop unused label defined in examples section in dt-bindings.
- Update compatible field in starfive_starlink_pmu.c to the
aforementioned.
Changes since v2:
- Change compatible field from generic "starfive,starlink-pmu"
to "starfive,starlink-500-pmu" with specific IP versioning
in bindings and driver.
- Fix warning '-Wmissing-prototypes' reported by kernel test robot,
by appending static to starlink_pmu_set_event_period() in
starfive_starlink_pmu.c.
Changes since v1:
- Change 'depends on SOC_STARFIVE' to 'depends on ARCH_STARFIVE'
in Kconfig
----
This patch series adds support for StarFive's Starlink Performance
Monitor Unit(PMU).
StarFive's StarLink PMU integrates one or more CPU cores with
a shared L3 memory system. The PMU supports overflow interrupt,
up to 16 programmable 64bit event counters, and an independent
64bit cycle counter.
StarLink PMU is accessed via MMIO.
Example Perf stat output:
[root@user]# perf stat -a -e /starfive_starlink_pmu/cycles/ \
-e /starfive_starlink_pmu/read_miss/ \
-e /starfive_starlink_pmu/read_hit/ \
-e /starfive_starlink_pmu/release_request/ \
-e /starfive_starlink_pmu/write_hit/ \
-e /starfive_starlink_pmu/write_miss/ \
-e /starfive_starlink_pmu/write_request/ \
-e /starfive_starlink_pmu/writeback/ \
-e /starfive_starlink_pmu/read_request/ \
-- openssl speed rsa2048
Doing 2048 bits private rsa's for 10s: 5 2048 bits private RSA's in
2.84s
Doing 2048 bits public rsa's for 10s: 169 2048 bits public RSA's in
2.42s
version: 3.0.11
built on: Tue Sep 19 13:02:31 2023 UTC
options: bn(64,64)
CPUINFO: N/A
sign verify sign/s verify/s
rsa 2048 bits 0.568000s 0.014320s 1.8 69.8
/////////
Performance counter stats for 'system wide':
649991998 starfive_starlink_pmu/cycles/
1009690 starfive_starlink_pmu/read_miss/
1079750 starfive_starlink_pmu/read_hit/
2089405 starfive_starlink_pmu/release_request/
129 starfive_starlink_pmu/write_hit/
70 starfive_starlink_pmu/write_miss/
194 starfive_starlink_pmu/write_request/
150080 starfive_starlink_pmu/writeback/
2089423 starfive_starlink_pmu/read_request/
27.062755678 seconds time elapsed
Ji Sheng Teoh (4):
perf: starfive: Add StarLink PMU support
dt-bindings: perf: starfive: Add JH8100 StarLink PMU
docs: perf: Add description for StarFive's StarLink PMU
MAINTAINERS: Add entry for StarFive StarLink PMU
Documentation/admin-guide/perf/index.rst | 1 +
.../perf/starfive_starlink_pmu.rst | 46 ++
.../perf/starfive,jh8100-starlink-pmu.yaml | 46 ++
MAINTAINERS | 7 +
drivers/perf/Kconfig | 9 +
drivers/perf/Makefile | 1 +
drivers/perf/starfive_starlink_pmu.c | 643 ++++++++++++++++++
7 files changed, 753 insertions(+)
create mode 100644 Documentation/admin-guide/perf/starfive_starlink_pmu.rst
create mode 100644 Documentation/devicetree/bindings/perf/starfive,jh8100-starlink-pmu.yaml
create mode 100644 drivers/perf/starfive_starlink_pmu.c
--
2.43.0
next reply other threads:[~2024-01-29 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 9:51 Ji Sheng Teoh [this message]
2024-01-29 9:51 ` [PATCH v6 1/4] perf: starfive: Add StarLink PMU support Ji Sheng Teoh
2024-02-23 11:26 ` Will Deacon
2024-02-24 1:12 ` JiSheng Teoh
2024-01-29 9:51 ` [PATCH v6 2/4] dt-bindings: perf: starfive: Add JH8100 StarLink PMU Ji Sheng Teoh
2024-01-29 9:51 ` [PATCH v6 3/4] docs: perf: Add description for StarFive's " Ji Sheng Teoh
2024-01-29 9:51 ` [PATCH v6 4/4] MAINTAINERS: Add entry for StarFive " Ji Sheng Teoh
2024-02-22 12:57 ` [PATCH v6 0/4] StarFive's StarLink PMU Support Will Deacon
2024-02-22 18:12 ` Palmer Dabbelt
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=20240129095141.3262366-1-jisheng.teoh@starfivetech.com \
--to=jisheng.teoh@starfivetech.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=ilkka@os.amperecomputing.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will@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