From: Agustin Vega-Frias <agustinv@codeaurora.org>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: Neil Leeder <neil.m.leeder@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
Timur Tabi <timur@codeaurora.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver
Date: Wed, 02 May 2018 10:20:19 -0400 [thread overview]
Message-ID: <93b3738c386c528193b158da0f85fd27@codeaurora.org> (raw)
In-Reply-To: <c1f9230b-8ff0-5b2e-def9-cbf6b2e2e99c@huawei.com>
On 2018-04-02 02:37, Yisheng Xie wrote:
> Hi Neil,
>
> On 2018/4/1 13:44, Neil Leeder wrote:
>> Hi Yisheng Xie,
>>
>> On 3/29/2018 03:03 AM, Yisheng Xie wrote:
>>>
>>> Hi Neil,
>>>
>>> On 2017/8/5 3:59, Neil Leeder wrote:
>>>> + mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM,
>>>> 0);
>>>> + mem_map_0 = devm_ioremap_resource(&pdev->dev, mem_resource_0);
>>>> +
>>> Can we use devm_ioremap instead? for the reg_base of smmu_pmu is
>>> IMPLEMENTATION DEFINED. If the reg of smmu_pmu is inside smmu,
>>> devm_ioremap_resource will failed and return -EBUSY, eg.:
>>>
>>> smmu reg ranges: 0x180000000 ~ 0x1801fffff
>>> its smmu_pmu reg ranges: 0x180001000 ~ 0x180001fff
>>>
>> Just to let you know that I no longer work at Qualcomm and I won't be
>> able to provide updates to this patchset. I expect that others from my
>> former team at Qualcomm will pick up ownership.
>
> Thanks for this infomation.
>
> hi Agustin and Timur,
>
> Is there any new status about this patchset?
>
Hi,
Apologies for the slow response.
We are having some internal discussions about when/if to do this.
I expect to have more clarity within a few weeks.
For what is worth let me take the opportunity to outline the approach
we would like to see for a V2 either developed by us or somebody else
in the community:
1. Rework to comply with the IORT spec changes.
2. Rework probing to extract extra information from the IORT table
about SMMU/device associations.
With this information and some perf user space work I think it's
possible
to have a single dynamic PMU node and use a similar approach to what
is
used in the Coresight drivers to pass the device we want to monitor
and
for the driver to find the PMU/PMCG. E.g.:
$ lspci
0001:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401
0002:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401
0002:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family
[ConnectX-3]
0003:00:00.0 PCI bridge: Airgo Networks, Inc. Device 0401
0003:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family
[ConnectX-3]
# Monitor TLB misses on root complex 2 (no stream filter is applied)
perf stat -a -e smmu/tlb_miss,@0002:00:00.0/ <workload>
# Monitor TLB misses on a device on root complex 2 (derive the stream
number from the RID)
perf stat -a -e smmu/tlb_miss,@0002:01:00.0/ <workload>
Thanks,
Agustín
--
Qualcomm Datacenter Technologies, Inc. on behalf of the Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a
Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-05-02 14:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 19:59 [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support Neil Leeder
2017-08-04 19:59 ` [PATCH 1/2] acpi: arm64: add iort support for PMCG Neil Leeder
2017-08-07 11:17 ` Robin Murphy
2017-08-07 20:52 ` Leeder, Neil
2017-08-07 16:44 ` Lorenzo Pieralisi
2017-08-07 21:00 ` Leeder, Neil
2018-01-30 10:39 ` Shameerali Kolothum Thodi
2018-01-30 18:00 ` Lorenzo Pieralisi
2018-01-31 12:10 ` Shameerali Kolothum Thodi
2018-01-31 12:34 ` Lorenzo Pieralisi
2017-08-04 19:59 ` [PATCH 2/2] perf: add arm64 smmuv3 pmu driver Neil Leeder
2017-08-07 14:31 ` Robin Murphy
2017-08-07 21:18 ` Leeder, Neil
2017-12-05 5:01 ` Linu Cherian
2018-03-29 7:03 ` Yisheng Xie
[not found] ` <e55ab4404143ea0b3cc4795a93e37480@codeaurora.org>
2018-04-01 5:44 ` Neil Leeder
2018-04-02 6:37 ` Yisheng Xie
2018-04-02 14:24 ` Hanjun Guo
2018-04-02 17:59 ` Neil Leeder
2018-04-03 1:15 ` Hanjun Guo
2018-04-04 11:35 ` Lorenzo Pieralisi
2018-05-02 14:20 ` Agustin Vega-Frias [this message]
2018-05-03 9:22 ` Shameerali Kolothum Thodi
2018-04-18 11:05 ` Shameerali Kolothum Thodi
2018-04-19 1:17 ` Yisheng Xie
2017-08-09 7:56 ` [PATCH 0/2] arm64 SMMUv3 PMU driver with IORT support Hanjun Guo
2017-08-09 15:48 ` Leeder, Neil
2017-08-10 1:26 ` Hanjun Guo
2017-08-11 3:28 ` Leeder, Neil
2017-10-12 10:58 ` Hanjun Guo
2017-10-12 11:05 ` Lorenzo Pieralisi
2017-10-12 11:11 ` Hanjun Guo
2017-10-31 23:33 ` Yury Norov
2017-11-02 20:38 ` Leeder, Neil
2017-12-10 2:35 ` Linu Cherian
2017-12-18 14:48 ` Robin Murphy
2017-12-18 15:39 ` Marc Zyngier
2017-12-19 6:55 ` Linu Cherian
2017-12-19 12:11 ` Marc Zyngier
2017-12-19 6:36 ` Linu Cherian
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=93b3738c386c528193b158da0f85fd27@codeaurora.org \
--to=agustinv@codeaurora.org \
--cc=broonie@kernel.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=neil.m.leeder@gmail.com \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=xieyisheng1@huawei.com \
/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