From: John Garry <john.garry@huawei.com>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>, <will@kernel.org>,
<mark.rutland@arm.com>
Cc: linuxarm@huawei.com, jolsa@redhat.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, qiangqing.zhang@nxp.com
Subject: Re: [PATCH] drivers/perf: hisi: Add identifier sysfs file
Date: Thu, 18 Jun 2020 10:18:42 +0100 [thread overview]
Message-ID: <086e0fd0-590b-8a95-5ac9-9d585e8a3342@huawei.com> (raw)
In-Reply-To: <089b4276-a247-5d39-4227-32629d3ee888@hisilicon.com>
On 18/06/2020 02:40, Shaokun Zhang wrote:
>> }
>>
>> + hha_pmu->identifier = readl(hha_pmu->base + HHA_VERSION);
> Since we are now refactoring the PMU framework, the PMU version offset
> is always the same except DDRC PMU and other uncore PMU modules will
> also use this, how about we do it as the common code:
>
> #define HISI_PMU_VERSION_REG 0x1CF0
> int hisi_uncore_pmu_version(struct hisi_pmu *hisi_pmu)
> {
> return readl(hisi_pmu->base + HISI_PMU_VERSION_REG);
> }
> EXPORT_SYMBOL_GPL(hisi_uncore_pmu_version);
Hi Shaokun,
Some points to make:
- It's hardly worth having a separate function to do this 1-line readl()
call, especially since it not even generic (DDRC is different)
- We would have to export it (or put in a common header file with static
inline keywords) - less exports are good
- with factoring out common code, it's good to reduce total code - this
change would increase it, AFAICS
- This is HW specific. The driver is currently layered such that all HW
specific stuff is in the HW driver (like hisi_uncore_ddrc_pmu.c), and
not library code (hisi_uncore_pmu.c). I don't see why you want to mix
that, like you're proposing in the framework revision you proposed
internally.
Thanks,
John
>
> hha_pmu->identifier = hisi_uncore_pmu_version(hha_pmu);
> we can remove the duplicated PMU version register definition in each module.
>
> Thanks,
> Shaokun
>
>> +
>> return 0;
>> }
>>
>> @@ -320,10 +323,23 @@ static const struct attribute_group hisi_hha_pmu_cpumask_attr_group = {
>> .attrs = hisi_hha_pmu_cpumask_attrs,
>> };
_______________________________________________
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:[~2020-06-18 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 13:05 [PATCH] drivers/perf: hisi: Add identifier sysfs file John Garry
2020-06-18 1:39 ` Joakim Zhang
2020-06-18 1:40 ` Shaokun Zhang
2020-06-18 9:18 ` John Garry [this message]
2020-07-14 8:32 ` Will Deacon
2020-07-15 8:23 ` John Garry
2020-07-15 8:28 ` Joakim Zhang
2020-07-15 8:30 ` Will Deacon
2020-10-01 8:34 ` John Garry
2020-09-01 10:18 ` Joakim Zhang
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=086e0fd0-590b-8a95-5ac9-9d585e8a3342@huawei.com \
--to=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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