linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: 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 3/5] driver/perf: Add identifier sysfs file for Yitian 710 DDR
Date: Mon, 1 May 2023 13:31:29 +0100	[thread overview]
Message-ID: <136984f7-b9a0-721f-3e31-f6ef840b0878@oracle.com> (raw)
In-Reply-To: <1682329456-19418-4-git-send-email-renyu.zj@linux.alibaba.com>

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 Yitian 710 DDR metric through the identifier.
> 
> Signed-off-by: Jing Zhang<renyu.zj@linux.alibaba.com>
> ---
>   drivers/perf/alibaba_uncore_drw_pmu.c | 27 +++++++++++++++++++++++++++
>   1 file changed, 27 insertions(+)
> 
> diff --git a/drivers/perf/alibaba_uncore_drw_pmu.c b/drivers/perf/alibaba_uncore_drw_pmu.c
> index a7689fe..fe075fd 100644
> --- a/drivers/perf/alibaba_uncore_drw_pmu.c
> +++ b/drivers/perf/alibaba_uncore_drw_pmu.c
> @@ -236,10 +236,37 @@ static ssize_t ali_drw_pmu_cpumask_show(struct device *dev,
>   	.attrs = ali_drw_pmu_cpumask_attrs,
>   };
>   
> +static ssize_t ali_drw_pmu_identifier_show(struct device *dev,
> +					struct device_attribute *attr,
> +					char *page)
> +{
> +	return sysfs_emit(page, "%s\n", "ali_drw_pmu");
> +}

Would there be anything more unique per implementation version? Having a 
constant like this means that all implementations will have same events 
from userspace PoV.

Thanks,
John

  reply	other threads:[~2023-05-01 12:31 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
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 [this message]
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=136984f7-b9a0-721f-3e31-f6ef840b0878@oracle.com \
    --to=john.g.garry@oracle.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=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).