From: Robin Murphy <robin.murphy@arm.com>
To: John Garry <john.garry@huawei.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
robh+dt@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org, uchida.jun@socionext.com,
leo.yan@linaro.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] perf/smmuv3: Synthesize IIDR from CoreSight ID registers
Date: Tue, 7 Dec 2021 12:04:32 +0000 [thread overview]
Message-ID: <766ac58a-ffb7-f673-709b-0f0f740f3cfd@arm.com> (raw)
In-Reply-To: <e60b15db-4e52-b5a6-1b17-203d250f1e65@huawei.com>
On 2021-12-07 09:14, John Garry wrote:
> On 17/11/2021 14:48, Jean-Philippe Brucker wrote:
>> From: Robin Murphy<robin.murphy@arm.com>
>>
>> The SMMU_PMCG_IIDR register was not present in older revisions of the
>> Arm SMMUv3 spec. On Arm Ltd. implementations, the IIDR value consists of
>> fields from several PIDR registers, allowing us to present a
>> standardized identifier to userspace.
>>
> So is there some userspace part to go with this now?
FWIW I've not looked into it - is it just a case of someone knocking out
some JSON from the MMU-600/700 TRMs, or is there still mroe to do? I had
the impression that *some* part of the process was stalled until
implementations can start providing meaningful IIDRs, but I wasn't sure
whether that was tooling or just data. I just work the low-level
enablement angle :)
Robin.
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: John Garry <john.garry@huawei.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
robh+dt@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org, uchida.jun@socionext.com,
leo.yan@linaro.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] perf/smmuv3: Synthesize IIDR from CoreSight ID registers
Date: Tue, 7 Dec 2021 12:04:32 +0000 [thread overview]
Message-ID: <766ac58a-ffb7-f673-709b-0f0f740f3cfd@arm.com> (raw)
In-Reply-To: <e60b15db-4e52-b5a6-1b17-203d250f1e65@huawei.com>
On 2021-12-07 09:14, John Garry wrote:
> On 17/11/2021 14:48, Jean-Philippe Brucker wrote:
>> From: Robin Murphy<robin.murphy@arm.com>
>>
>> The SMMU_PMCG_IIDR register was not present in older revisions of the
>> Arm SMMUv3 spec. On Arm Ltd. implementations, the IIDR value consists of
>> fields from several PIDR registers, allowing us to present a
>> standardized identifier to userspace.
>>
> So is there some userspace part to go with this now?
FWIW I've not looked into it - is it just a case of someone knocking out
some JSON from the MMU-600/700 TRMs, or is there still mroe to do? I had
the impression that *some* part of the process was stalled until
implementations can start providing meaningful IIDRs, but I wasn't sure
whether that was tooling or just data. I just work the low-level
enablement angle :)
Robin.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: John Garry <john.garry@huawei.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
robh+dt@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org, uchida.jun@socionext.com,
leo.yan@linaro.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] perf/smmuv3: Synthesize IIDR from CoreSight ID registers
Date: Tue, 7 Dec 2021 12:04:32 +0000 [thread overview]
Message-ID: <766ac58a-ffb7-f673-709b-0f0f740f3cfd@arm.com> (raw)
In-Reply-To: <e60b15db-4e52-b5a6-1b17-203d250f1e65@huawei.com>
On 2021-12-07 09:14, John Garry wrote:
> On 17/11/2021 14:48, Jean-Philippe Brucker wrote:
>> From: Robin Murphy<robin.murphy@arm.com>
>>
>> The SMMU_PMCG_IIDR register was not present in older revisions of the
>> Arm SMMUv3 spec. On Arm Ltd. implementations, the IIDR value consists of
>> fields from several PIDR registers, allowing us to present a
>> standardized identifier to userspace.
>>
> So is there some userspace part to go with this now?
FWIW I've not looked into it - is it just a case of someone knocking out
some JSON from the MMU-600/700 TRMs, or is there still mroe to do? I had
the impression that *some* part of the process was stalled until
implementations can start providing meaningful IIDRs, but I wasn't sure
whether that was tooling or just data. I just work the low-level
enablement angle :)
Robin.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-07 12:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:48 [PATCH v2 0/3] perf/smmuv3: Support devicetree Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` [PATCH v2 1/3] dt-bindings: Add Arm SMMUv3 PMCG binding Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` [PATCH v2 2/3] perf/smmuv3: Add devicetree support Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` [PATCH v2 3/3] perf/smmuv3: Synthesize IIDR from CoreSight ID registers Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-11-17 14:48 ` Jean-Philippe Brucker
2021-12-07 9:14 ` John Garry
2021-12-07 9:14 ` John Garry
2021-12-07 9:14 ` John Garry via iommu
2021-12-07 12:04 ` Robin Murphy [this message]
2021-12-07 12:04 ` Robin Murphy
2021-12-07 12:04 ` Robin Murphy
2021-12-07 12:28 ` John Garry
2021-12-07 12:28 ` John Garry
2021-12-07 12:28 ` John Garry via iommu
2021-12-07 12:48 ` Robin Murphy
2021-12-07 12:48 ` Robin Murphy
2021-12-07 12:48 ` Robin Murphy
2021-12-07 13:20 ` Leo Yan
2021-12-07 13:20 ` Leo Yan
2021-12-07 13:20 ` Leo Yan
2021-12-07 13:46 ` Robin Murphy
2021-12-07 13:46 ` Robin Murphy
2021-12-07 13:46 ` Robin Murphy
2021-12-07 13:59 ` Leo Yan
2021-12-07 13:59 ` Leo Yan
2021-12-07 13:59 ` Leo Yan
2021-12-07 14:00 ` John Garry
2021-12-07 14:00 ` John Garry
2021-12-07 14:00 ` John Garry via iommu
2021-12-07 14:04 ` Leo Yan
2021-12-07 14:04 ` Leo Yan
2021-12-07 14:04 ` Leo Yan
2021-12-14 14:04 ` [PATCH v2 0/3] perf/smmuv3: Support devicetree Will Deacon
2021-12-14 14:04 ` Will Deacon
2021-12-14 14:04 ` 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=766ac58a-ffb7-f673-709b-0f0f740f3cfd@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=uchida.jun@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.