From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org, mark.rutland@arm.com
Cc: lorenzo.pieralisi@arm.com, sudeep.holla@arm.com,
linux-arm-kernel@lists.infradead.org, jean-philippe@linaro.org,
leo.yan@linaro.org, noda.akio@socionext.com
Subject: [PATCH 0/6] perf: Arm SMMU PMU driver
Date: Thu, 17 Feb 2022 14:24:14 +0000 [thread overview]
Message-ID: <cover.1645106346.git.robin.murphy@arm.com> (raw)
Hi all,
Since our friends at Linaro had some interest in the area, I've dug up
and finished off my old SMMUv1/v2 PMU driver, now with a slightly less
terrible DT binding to boot. Patch #1 involves a general refactoring of
the IRQ setup code in arm-smmu which also now serves to remove the
general dependency on explicit IRQ resources for of_platform devices.
ACPI support via IORT (patch #2) is pleasingly trivial, but does have a
hard dependency on the previous patch, otherwise SMMU context
interrupts may get messed up.
The driver itself in patch #5 is still largely a time capsule of me
learning the PMU APIs 5 years ago (as a warm-up for arm-cmn). I've
mostly just added IRQ affinity support (which I didn't yet fully
understand at the time) and tweaked a few comments. I'm pretty confident
all the testing I did back then is still valid, so I've just run some
quick sanity checks with patch #6 to verify the new DT binding.
Cheers,
Robin.
Robin Murphy (6):
iommu/arm-smmu: Account for PMU interrupts
acpi/iort: Register SMMUv2 PMU interrupts
iommu/arm-smmu: Add DT PMU support
iommu/smmu: Create child devices for PMUs
perf: Add ARM SMMU PMU driver
arm64: dts: Add SMMU PMUs to Juno
.../devicetree/bindings/iommu/arm,smmu.yaml | 19 +-
arch/arm64/boot/dts/arm/juno-base.dtsi | 26 +-
drivers/acpi/arm64/iort.c | 18 +-
drivers/iommu/arm/arm-smmu/arm-smmu.c | 143 ++--
drivers/iommu/arm/arm-smmu/arm-smmu.h | 5 +-
drivers/perf/Kconfig | 24 +-
drivers/perf/Makefile | 1 +
drivers/perf/arm-smmu-pmu.c | 732 ++++++++++++++++++
8 files changed, 896 insertions(+), 72 deletions(-)
create mode 100644 drivers/perf/arm-smmu-pmu.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:[~2022-02-17 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 14:24 Robin Murphy [this message]
2022-02-17 14:24 ` [PATCH 1/6] iommu/arm-smmu: Account for PMU interrupts Robin Murphy
2022-02-17 14:24 ` [PATCH 2/6] acpi/iort: Register SMMUv2 " Robin Murphy
2022-02-17 14:24 ` [PATCH 3/6] iommu/arm-smmu: Add DT PMU support Robin Murphy
2022-03-02 15:33 ` Rob Herring
2022-03-02 17:03 ` Robin Murphy
2022-02-17 14:24 ` [PATCH 4/6] iommu/smmu: Create child devices for PMUs Robin Murphy
2022-02-17 14:24 ` [PATCH 5/6] perf: Add ARM SMMU PMU driver Robin Murphy
2022-02-17 14:24 ` [PATCH 6/6] arm64: dts: Add SMMU PMUs to Juno Robin Murphy
2022-03-07 22:03 ` [PATCH 0/6] perf: Arm SMMU PMU driver Will Deacon
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.1645106346.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=jean-philippe@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=noda.akio@socionext.com \
--cc=sudeep.holla@arm.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).