mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kajoljain <kjain@linux.ibm.com>
To: John Garry <john.garry@huawei.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org, irogers@google.com,
	yao.jin@linux.intel.com, yeyunfeng@huawei.com
Cc: linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 2/2] perf jevents: Add test for arch std events
Date: Fri, 23 Oct 2020 13:27:09 +0530	[thread overview]
Message-ID: <1f54b1c5-e788-57f1-b2d4-c0d33af85f00@linux.ibm.com> (raw)
In-Reply-To: <1603364547-197086-3-git-send-email-john.garry@huawei.com>



On 10/22/20 4:32 PM, John Garry wrote:
> Recently there was an undetected breakage for std arch event support.
> 
> Add support in "PMU events" testcase to detect such breakages.
> 
> For this, the "test" arch needs has support added to process std arch
> events. And a test event is added for the test, ifself.
> 
> Also add a few code comments to help understand the code a bit better.

Patch looks good to me.

Reviewed-By: Kajol Jain<kjain@linux.ibm.com>

Thanks,
Kajol Jain
> 
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
>  .../perf/pmu-events/arch/test/arch-std-events.json |  8 ++++++++
>  .../perf/pmu-events/arch/test/test_cpu/cache.json  |  5 +++++
>  tools/perf/pmu-events/jevents.c                    |  4 ++++
>  tools/perf/tests/pmu-events.c                      | 14 ++++++++++++++
>  4 files changed, 31 insertions(+)
>  create mode 100644 tools/perf/pmu-events/arch/test/arch-std-events.json
>  create mode 100644 tools/perf/pmu-events/arch/test/test_cpu/cache.json
> 
> diff --git a/tools/perf/pmu-events/arch/test/arch-std-events.json b/tools/perf/pmu-events/arch/test/arch-std-events.json
> new file mode 100644
> index 000000000000..43f6f729d6ae
> --- /dev/null
> +++ b/tools/perf/pmu-events/arch/test/arch-std-events.json
> @@ -0,0 +1,8 @@
> +[
> +    {
> +        "PublicDescription": "Attributable Level 3 cache access, read",
> +        "EventCode": "0x40",
> +        "EventName": "L3_CACHE_RD",
> +        "BriefDescription": "L3 cache access, read"
> +    }
> +]
> diff --git a/tools/perf/pmu-events/arch/test/test_cpu/cache.json b/tools/perf/pmu-events/arch/test/test_cpu/cache.json
> new file mode 100644
> index 000000000000..036d0efdb2bb
> --- /dev/null
> +++ b/tools/perf/pmu-events/arch/test/test_cpu/cache.json
> @@ -0,0 +1,5 @@
> +[
> +    {
> +	 "ArchStdEvent": "L3_CACHE_RD"
> +    }
> +]
> \ No newline at end of file
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index 7326c14c4623..72cfa3b5046d 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -1162,6 +1162,10 @@ int main(int argc, char *argv[])
>  
>  	sprintf(ldirname, "%s/test", start_dirname);
>  
> +	rc = nftw(ldirname, preprocess_arch_std_files, maxfds, 0);
> +	if (rc)
> +		goto err_processing_std_arch_event_dir;
> +
>  	rc = nftw(ldirname, process_one_file, maxfds, 0);
>  	if (rc)
>  		goto err_processing_dir;
> diff --git a/tools/perf/tests/pmu-events.c b/tools/perf/tests/pmu-events.c
> index d3517a74d95e..ad2b21591275 100644
> --- a/tools/perf/tests/pmu-events.c
> +++ b/tools/perf/tests/pmu-events.c
> @@ -14,8 +14,10 @@
>  #include "util/parse-events.h"
>  
>  struct perf_pmu_test_event {
> +	/* used for matching against events from generated pmu-events.c */
>  	struct pmu_event event;
>  
> +	/* used for matching against event aliases */
>  	/* extra events for aliases */
>  	const char *alias_str;
>  
> @@ -78,6 +80,17 @@ static struct perf_pmu_test_event test_cpu_events[] = {
>  		.alias_str = "umask=0,(null)=0x30d40,event=0x3a",
>  		.alias_long_desc = "Number of Enhanced Intel SpeedStep(R) Technology (EIST) transitions",
>  	},
> +	{
> +		.event = {
> +			.name = "l3_cache_rd",
> +			.event = "event=0x40",
> +			.desc = "L3 cache access, read",
> +			.long_desc = "Attributable Level 3 cache access, read",
> +			.topic = "cache",
> +		},
> +		.alias_str = "event=0x40",
> +		.alias_long_desc = "Attributable Level 3 cache access, read",
> +	},
>  	{ /* sentinel */
>  		.event = {
>  			.name = NULL,
> @@ -357,6 +370,7 @@ static int __test__pmu_event_aliases(char *pmu_name, int *count)
>  }
>  
>  
> +/* Test that aliases generated are as expected */
>  static int test_aliases(void)
>  {
>  	struct perf_pmu *pmu = NULL;
> 

  reply	other threads:[~2020-10-23  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 11:02 [PATCH v2 0/2] perf PMU events test: Add scenario " John Garry
2020-10-22 11:02 ` [PATCH v2 1/2] perf jevents: Tidy error handling John Garry
2020-10-23  7:49   ` kajoljain
2020-10-22 11:02 ` [PATCH v2 2/2] perf jevents: Add test for arch std events John Garry
2020-10-23  7:57   ` kajoljain [this message]
2020-10-27 16:34 ` [PATCH v2 0/2] perf PMU events test: Add scenario " Arnaldo Carvalho de Melo

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=1f54b1c5-e788-57f1-b2d4-c0d33af85f00@linux.ibm.com \
    --to=kjain@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yao.jin@linux.intel.com \
    --cc=yeyunfeng@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

Powered by JetHome