From: Robin Murphy <robin.murphy@arm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
Joerg Roedel <joro@8bytes.org>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: ARM_SMMU_V3_PMU should depend on ARM_SMMU_V3
Date: Wed, 16 Aug 2023 12:23:30 +0100 [thread overview]
Message-ID: <2e076cb5-1e31-10b2-9f33-79a825ac9c11@arm.com> (raw)
In-Reply-To: <0f8ac07472f4161c71247742acb2303f9cf91396.1692113438.git.geert+renesas@glider.be>
On 2023-08-15 16:36, Geert Uytterhoeven wrote:
> There is no point in monitoring transactions passing through the SMMU
> when ARM Ltd. System MMU Version 3 (SMMUv3) Support is disabled.
> Hence replace the dependency on ARM64 by a dependency on ARM_SMMU_V3
> (which implies the former).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> This caught my eye after commit 7c3f204e544dfa37 ("perf/smmuv3: Remove
> build dependency on ACPI") in arm64/for-next/core.
>
> Perhaps my understanding is wrong? Is there anything to monitor when
> ARM_SMMU_V3=n?
Yes, at least TBU event 1 still counts bypass transactions even when the
SMMU is disabled, so PMCGs can be useful as basic traffic monitors in
their own right. Plus the original design intent was that PMCGs may also
be implemented by other things that interact with the SMMU, like
ATS-capable PCIe root complexes, or devices with their own internal
TLBs, thus they could potentially count any manner of
implementation-defined events that aren't necessarily related to SMMU
translation.
Thanks,
Robin.
> drivers/perf/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig
> index 273d67ecf6d2530f..c33324692fbf0141 100644
> --- a/drivers/perf/Kconfig
> +++ b/drivers/perf/Kconfig
> @@ -92,7 +92,7 @@ config ARM_PMU_ACPI
>
> config ARM_SMMU_V3_PMU
> tristate "ARM SMMUv3 Performance Monitors Extension"
> - depends on ARM64 || (COMPILE_TEST && 64BIT)
> + depends on ARM_SMMU_V3 || (COMPILE_TEST && 64BIT)
> depends on GENERIC_MSI_IRQ
> help
> Provides support for the ARM SMMUv3 Performance Monitor Counter
next prev parent reply other threads:[~2023-08-16 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 15:36 Geert Uytterhoeven
2023-08-16 11:23 ` Robin Murphy [this message]
2023-08-16 11:36 ` Geert Uytterhoeven
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=2e076cb5-1e31-10b2-9f33-79a825ac9c11@arm.com \
--to=robin.murphy@arm.com \
--cc=geert+renesas@glider.be \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=vincent.whitchurch@axis.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
all inboxes | Powered by JetHome®