From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Besar Wicaksono <bwicaksono@nvidia.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"thanu.rangarajan@arm.com" <thanu.rangarajan@arm.com>,
"Michael.Williams@arm.com" <Michael.Williams@arm.com>,
Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Vikram Sethi <vsethi@nvidia.com>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
"mike.leach@linaro.org" <mike.leach@linaro.org>,
"leo.yan@linaro.org" <leo.yan@linaro.org>
Subject: Re: [PATCH v4 2/2] perf: arm_cspmu: Add support for NVIDIA SCF and MCF attribute
Date: Wed, 28 Sep 2022 11:47:11 +0100 [thread overview]
Message-ID: <739570af-b90a-aea6-ee56-cb1d5da48c97@arm.com> (raw)
In-Reply-To: <SJ0PR12MB5676A36BC125A9873F74E697A0549@SJ0PR12MB5676.namprd12.prod.outlook.com>
On 28/09/2022 02:38, Besar Wicaksono wrote:
>
>
>> -----Original Message-----
>> From: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Sent: Tuesday, September 27, 2022 6:43 AM
>> To: Besar Wicaksono <bwicaksono@nvidia.com>; robin.murphy@arm.com;
>> catalin.marinas@arm.com; will@kernel.org; mark.rutland@arm.com
>> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
>> linux-tegra@vger.kernel.org; sudeep.holla@arm.com;
>> thanu.rangarajan@arm.com; Michael.Williams@arm.com; Thierry Reding
>> <treding@nvidia.com>; Jonathan Hunter <jonathanh@nvidia.com>; Vikram
>> Sethi <vsethi@nvidia.com>; mathieu.poirier@linaro.org;
>> mike.leach@linaro.org; leo.yan@linaro.org
>> Subject: Re: [PATCH v4 2/2] perf: arm_cspmu: Add support for NVIDIA SCF
>> and MCF attribute
>>
>> External email: Use caution opening links or attachments
>>
>>
>> On 14/08/2022 19:23, Besar Wicaksono wrote:
>>> Add support for NVIDIA System Cache Fabric (SCF) and Memory Control
>>> Fabric (MCF) PMU attributes for CoreSight PMU implementation in
>>> NVIDIA devices.
>>>
>>> Signed-off-by: Besar Wicaksono <bwicaksono@nvidia.com>
>>> +struct nv_cspmu_match {
>>> + u32 prodid;
>>> + u32 prodid_mask;
>>> + u64 filter_mask;
>>> + const char *name_pattern;
>>> + enum nv_cspmu_name_fmt name_fmt;
>>> + struct attribute **event_attr;
>>> + struct attribute **format_attr;
>>> +};
>>> +
>>> +static const struct nv_cspmu_match nv_cspmu_match[] = {
>>
>> Similar coding style nit below.
>>
>
> Sure, I will update this.
>
>>
>> Otherwise,
>>
>> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> Thanks!
>
> Unfortunately, we need to update the name of the PMUs and remove
> some of the attributes in NVIDIA implementation. This requires a change
> in nvidia_cspmu.c and nvidia-pmu.rst. I hope you are fine if I include this
> change on v5 patch.
That should be fine.
Suzuki
next prev parent reply other threads:[~2022-09-28 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 18:23 [PATCH v4 0/2] perf: ARM CoreSight PMU support Besar Wicaksono
2022-08-14 18:23 ` [PATCH v4 1/2] perf: arm_cspmu: Add support for ARM CoreSight PMU driver Besar Wicaksono
2022-09-22 13:52 ` Will Deacon
2022-09-27 3:59 ` Besar Wicaksono
2022-09-28 8:31 ` Michael Williams (ATG)
2022-09-27 11:39 ` Suzuki K Poulose
2022-09-28 1:27 ` Besar Wicaksono
2022-08-14 18:23 ` [PATCH v4 2/2] perf: arm_cspmu: Add support for NVIDIA SCF and MCF attribute Besar Wicaksono
2022-09-27 11:42 ` Suzuki K Poulose
2022-09-28 1:38 ` Besar Wicaksono
2022-09-28 10:47 ` Suzuki K Poulose [this message]
2022-08-23 17:24 ` [PATCH v4 0/2] perf: ARM CoreSight PMU support Besar Wicaksono
2022-09-22 13:54 ` 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=739570af-b90a-aea6-ee56-cb1d5da48c97@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Michael.Williams@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=jonathanh@nvidia.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
--cc=thanu.rangarajan@arm.com \
--cc=treding@nvidia.com \
--cc=vsethi@nvidia.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).