From: Robin Murphy <robin.murphy@arm.com>
To: John Garry <john.g.garry@oracle.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Ian Rogers <irogers@google.com>, Will Deacon <will@kernel.org>,
Shuai Xue <xueshuai@linux.alibaba.com>
Cc: James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
Zhuo Song <zhuo.song@linux.alibaba.com>
Subject: Re: [PATCH v2 1/5] driver/perf: Add identifier sysfs file for CMN
Date: Thu, 4 May 2023 10:47:53 +0100 [thread overview]
Message-ID: <12bf4a7f-e99c-47cf-e8e4-e2700db6c5c9@arm.com> (raw)
In-Reply-To: <df63b597-4355-b9fc-6002-5a390b1a56f5@oracle.com>
On 2023-05-01 13:38, John Garry wrote:
> On 24/04/2023 10:44, Jing Zhang wrote:
>> To allow userspace to identify the specific implementation of the device,
>> add an "identifier" sysfs file.
>>
>> The perf tool can match the arm CMN metric through the identifier.
>>
>> Signed-off-by: Jing Zhang<renyu.zj@linux.alibaba.com>
>> ---
>> drivers/perf/arm-cmn.c | 49
>> +++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 49 insertions(+)
>>
>> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
>> index c968986..f425610 100644
>> --- a/drivers/perf/arm-cmn.c
>> +++ b/drivers/perf/arm-cmn.c
>> @@ -334,6 +334,7 @@ struct arm_cmn {
>> struct pmu pmu;
>> struct dentry *debug;
>> + const char *identifier;
>> };
>> #define to_cmn(p) container_of(p, struct arm_cmn, pmu)
>> @@ -1168,10 +1169,41 @@ static ssize_t arm_cmn_cpumask_show(struct
>> device *dev,
>> .attrs = arm_cmn_cpumask_attrs,
>> };
>> +static ssize_t arm_cmn_identifier_show(struct device *dev,
>> + struct device_attribute *attr, char *buf)
>> +{
>> + struct arm_cmn *cmn = to_cmn(dev_get_drvdata(dev));
>> +
>> + return sysfs_emit(buf, "%s\n", cmn->identifier);
>> +}
>> +
>> +static umode_t arm_cmn_identifier_attr_visible(struct kobject *kobj,
>> + struct attribute *attr, int n)
>> +{
>> + struct device *dev = kobj_to_dev(kobj);
>> + struct arm_cmn *cmn = to_cmn(dev_get_drvdata(dev));
>> +
>> + if (cmn->identifier == NULL)
>> + return 0;
>
> nit: generally if (!val) is preferred
Although either way it can only be NULL in cases of memory corruption or
developers making broken changes to the driver, neither of which are
worth pretending to defend against.
>> + return attr->mode;
>> +};
>> +
>> +static struct device_attribute arm_cmn_identifier_attr =
>> +__ATTR(identifier, 0444, arm_cmn_identifier_show, NULL);
>> +
>> +static struct attribute *arm_cmn_identifier_attrs[] = {
>> + &arm_cmn_identifier_attr.attr,
>> + NULL
>> +};
>> +
>> +static struct attribute_group arm_cmn_identifier_attr_group = {
>> + .attrs = arm_cmn_identifier_attrs,
>> + .is_visible = arm_cmn_identifier_attr_visible
>> +};
>> +
>> static const struct attribute_group *arm_cmn_attr_groups[] = {
>> &arm_cmn_event_attrs_group,
>> &arm_cmn_format_attrs_group,
>> &arm_cmn_cpumask_attr_group,
>> + &arm_cmn_identifier_attr_group,
>> NULL
>> };
>> @@ -2241,6 +2273,22 @@ static int arm_cmn600_of_probe(struct
>> device_node *np)
>> return of_property_read_u32(np, "arm,root-node", &rootnode) ?:
>> rootnode;
>> }
>> +const char *arm_cmn_identifier(unsigned long model)
>> +{
>> + switch (model) {
>> + case CMN600:
>> + return "cmn600";
>> + case CMN650:
>> + return "cmn650";
>> + case CMN700:
>> + return "cmn700";
>> + case CI700:
>> + return "ci700";
>> + default:
>> + return NULL;
>> + }
>
> nit: I think that it would be nicer to have this per-model string stored
> statically in arm_cmn_acpi_match[].driver_data and
> arm_cmn_of_match[].data, so we have a straight lookup
Again, I'm not really convinced how useful this coarse per-model scheme
is - for instance, in terms of many events, CMN-600 r3 is closer to
CMN-650 than it is to CMN-600 r1, so what exactly would "CMN-600" mean
to the user?
Thanks,
Robin.
>> +}
>> +
>> static int arm_cmn_probe(struct platform_device *pdev)
>> {
>> struct arm_cmn *cmn;
>> @@ -2254,6 +2302,7 @@ static int arm_cmn_probe(struct platform_device
>> *pdev)
>> cmn->dev = &pdev->dev;
>> cmn->model = (unsigned long)device_get_match_data(cmn->dev);
>> + cmn->identifier = arm_cmn_identifier(cmn->model);
>> platform_set_drvdata(pdev, cmn);
>
>
> _______________________________________________
> 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:[~2023-05-04 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:44 [PATCH v2 0/5] Add JSON metrics for arm CMN and Yitian710 DDR Jing Zhang
2023-04-24 9:44 ` [PATCH v2 1/5] driver/perf: Add identifier sysfs file for CMN Jing Zhang
2023-05-01 12:38 ` John Garry
2023-05-04 9:47 ` Robin Murphy [this message]
2023-05-04 11:02 ` John Garry
2023-05-04 12:15 ` Robin Murphy
2023-05-05 12:24 ` John Garry
2023-05-08 9:14 ` Jing Zhang
2023-04-24 9:44 ` [PATCH v2 2/5] perf vendor events: Add JSON metrics for CMN-700 Jing Zhang
2023-05-01 12:27 ` John Garry
2023-05-08 11:16 ` Jing Zhang
2023-04-24 9:44 ` [PATCH v2 3/5] driver/perf: Add identifier sysfs file for Yitian 710 DDR Jing Zhang
2023-05-01 12:31 ` John Garry
2023-05-08 11:35 ` Jing Zhang
2023-05-04 7:21 ` Shuai Xue
2023-04-24 9:44 ` [PATCH v2 4/5] perf jevents: Add support for Yitian 710 DDR PMU aliasing Jing Zhang
2023-05-01 12:29 ` John Garry
2023-05-04 7:18 ` Shuai Xue
2023-05-08 11:39 ` Jing Zhang
2023-04-24 9:44 ` [PATCH v2 5/5] perf vendor events: Add JSON metrics for Yitian 710 DDR Jing Zhang
2023-05-01 12:28 ` John Garry
2023-05-04 7:31 ` Shuai Xue
2023-05-08 11:40 ` Jing Zhang
2023-04-29 21:01 ` [PATCH v2 0/5] Add JSON metrics for arm CMN and Yitian710 DDR Ian Rogers
2023-05-08 11:19 ` Jing 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=12bf4a7f-e99c-47cf-e8e4-e2700db6c5c9@arm.com \
--to=robin.murphy@arm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--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 \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).