From: John Garry <john.garry@huawei.com>
To: Leo Yan <leo.yan@linaro.org>, <linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Question: SMMUv3 PMU event aliasing
Date: Mon, 8 Nov 2021 12:41:33 +0000 [thread overview]
Message-ID: <8b24f36b-6459-c13c-bf19-b9f588eb6b8e@huawei.com> (raw)
In-Reply-To: <20211108121941.GC1267967@leoy-ThinkPad-X240s>
On 08/11/2021 12:19, Leo Yan wrote:
> Hi John,
>
> [ + mailing list ]
Hi Leo,
>
> I'd like to confirm the latest upstream status for SMMUv3 PMU event
> aliasing.
>
> I see the patch set v6 of "perf pmu-events: Support event aliasing for
> system PMUs" [1] has been landed on the mainline kernel, and as an
> example, imx8mm DDR PMU has been supported as system PMU [2].
>
> On the other hand, I can see patch set 5 contains the SMMUv3 PMU event
> aliasing with patch "perf vendor events arm64: Add Architected events
> smmuv3-pmcg.json" [3], but this patch was left out in patch set 6 and
> it's never landed on the mainline kernel.
>
> Could you share current status (or plan) for upstreaming SMMUv3 PMU
> event alias? Or if there have any block issue to prevent merging the
> changes in the mainline kernel?
This feature should be supported in the SMMUv3 PMU kernel driver and
perf tool.
However it relies on the SMMU PMU identifier sysfs file to work. This
relies on SMMU_PMCG_IIDR being set, which is introduced latest spec,
which not much HW will support yet - see commit 2c255223362e. In theory
we don't need that for the fixed, non-IMPDEF events, but I did not
complicate perf tool with that mixed support.
That's the reason for which I paused smmuv3-pmcg.json upstream in [3]. I
will revive that for new gen HW when concrete IMPDEF events known and
shared.
Thanks,
John
>
> Thanks for your help!
>
> Leo
>
> [1] https://lore.kernel.org/lkml/1607080216-36968-1-git-send-email-john.garry@huawei.com/
> [2] pmu-events/arch/arm64/freescale/imx8mm/sys/ddrc.json
> [3] https://lore.kernel.org/lkml/1604666153-4187-6-git-send-email-john.garry@huawei.com/
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2021-11-08 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211108121941.GC1267967@leoy-ThinkPad-X240s>
2021-11-08 12:41 ` John Garry [this message]
2021-11-09 1:48 ` Question: SMMUv3 PMU event aliasing Leo Yan
2021-11-09 11:32 ` 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=8b24f36b-6459-c13c-bf19-b9f588eb6b8e@huawei.com \
--to=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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