From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, tuanphan@os.amperecomputing.com,
tsahee@amazon.com, harb@amperecomputing.com, james.yang@arm.com,
alisaidi@amazon.com
Subject: [PATCH 0/2] Arm CMN-600 PMU driver
Date: Wed, 5 Aug 2020 13:56:48 +0100 [thread overview]
Message-ID: <cover.1596631695.git.robin.murphy@arm.com> (raw)
Hi all,
At long last, here's an initial cut of the CMN PMU driver that's been
festering in on-and-off development for years. It should be functionally
complete now, although there is still scope for improving the current
implementation (e.g. watchpoint register allocation could be cleverer).
Of particular interest at this point is the user interface - is it
sufficiently complete and useful? Is there any need for a third event
targeting method in between "single node ID" and "all nodes"? Is it
worth templating watchpoints by port and channel to mimic XP events? Do
we want to expose watchpoint-based bandwidth events as synthetic per-node
events? Not all of that would need to be implemented right now so as to
further stall upstreaming, but I really want to make sure that the initial
interface is solid and any further enhancements can cleanly extend it,
rather than painting ourselves into a corner in terms of ABI support.
Robin.
Robin Murphy (2):
perf: Add Arm CMN-600 DT binding
perf: Add Arm CMN-600 PMU driver
Documentation/admin-guide/perf/arm-cmn.rst | 65 +
Documentation/admin-guide/perf/index.rst | 1 +
.../devicetree/bindings/perf/arm-cmn.yaml | 57 +
drivers/perf/Kconfig | 7 +
drivers/perf/Makefile | 1 +
drivers/perf/arm-cmn.c | 1653 +++++++++++++++++
6 files changed, 1784 insertions(+)
create mode 100644 Documentation/admin-guide/perf/arm-cmn.rst
create mode 100644 Documentation/devicetree/bindings/perf/arm-cmn.yaml
create mode 100644 drivers/perf/arm-cmn.c
--
2.28.0.dirty
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-08-05 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 12:56 Robin Murphy [this message]
2020-08-05 12:56 ` [PATCH 1/2] perf: Add Arm CMN-600 DT binding Robin Murphy
2020-08-13 2:34 ` Rob Herring
2020-08-05 12:56 ` [PATCH 2/2] perf: Add Arm CMN-600 PMU driver Robin Murphy
2020-09-07 10:45 ` Will Deacon
2020-09-07 11:23 ` John Garry
2020-09-07 13:27 ` Robin Murphy
2020-09-07 14:29 ` John Garry
[not found] <09BE24FF-DF48-49C5-AAC4-669372276200@amazon.com>
[not found] ` <082F0C98-4B73-4215-8B42-0C1B31780350@amperemail.onmicrosoft.com>
2020-09-18 13:06 ` [PATCH 0/2] " Robin Murphy
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=cover.1596631695.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=alisaidi@amazon.com \
--cc=devicetree@vger.kernel.org \
--cc=harb@amperecomputing.com \
--cc=james.yang@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=tsahee@amazon.com \
--cc=tuanphan@os.amperecomputing.com \
--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;
as well as URLs for NNTP newsgroup(s).