All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: Russell Currey <ruscur@russell.cc>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] selftests/powerpc: Fix L1D flushing tests for Power10
Date: Wed, 24 Feb 2021 11:42:47 +1100	[thread overview]
Message-ID: <878s7epa7s.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <20210223070227.2916871-1-ruscur@russell.cc>

Russell Currey <ruscur@russell.cc> writes:

> The rfi_flush and entry_flush selftests work by using the PM_LD_MISS_L1
> perf event to count L1D misses.  The value of this event has changed
> over time:
>
> - Power7 uses 0x400f0
> - Power8 and Power9 use both 0x400f0 and 0x3e054
> - Power10 uses only 0x3e054
>
> Rather than relying on raw values, configure perf to count L1D read
> misses in the most explicit way available.
>
> This fixes the selftests to work on systems without 0x400f0 as
> PM_LD_MISS_L1, and should change no behaviour for systems that the tests
> already worked on.
>
> The only potential downside is that referring to a specific perf event
> requires PMU support implemented in the kernel for that platform.

So, IIUC:

 - if you used raw events and ran the binary on a P10 system using an
   older kernel that did not support P10 PMU events, you would still get
   valid results
 - but, if the HW perf event changes again, we have the same issue with
   failing tests

vs

 - if you use symbolic events and run the binary on a P10 system using
   an older kernel that does not support P10 PMU events, you would not
   be able to run the test.
 - but, if the HW perf event changes again, the test will continue to
   work. 


This seems like the correct tradeoff to make.

Having spent some quality time with these tests in the past:

Acked-by: Daniel Axtens <dja@axtens.net>

Kind regards,
Daniel

>
> Signed-off-by: Russell Currey <ruscur@russell.cc>
> ---
> v2: Move away from raw events as suggested by mpe
>
>  tools/testing/selftests/powerpc/security/entry_flush.c | 2 +-
>  tools/testing/selftests/powerpc/security/flush_utils.h | 4 ++++
>  tools/testing/selftests/powerpc/security/rfi_flush.c   | 2 +-
>  3 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/powerpc/security/entry_flush.c b/tools/testing/selftests/powerpc/security/entry_flush.c
> index 78cf914fa321..68ce377b205e 100644
> --- a/tools/testing/selftests/powerpc/security/entry_flush.c
> +++ b/tools/testing/selftests/powerpc/security/entry_flush.c
> @@ -53,7 +53,7 @@ int entry_flush_test(void)
>  
>  	entry_flush = entry_flush_orig;
>  
> -	fd = perf_event_open_counter(PERF_TYPE_RAW, /* L1d miss */ 0x400f0, -1);
> +	fd = perf_event_open_counter(PERF_TYPE_HW_CACHE, PERF_L1D_READ_MISS_CONFIG, -1);
>  	FAIL_IF(fd < 0);
>  
>  	p = (char *)memalign(zero_size, CACHELINE_SIZE);
> diff --git a/tools/testing/selftests/powerpc/security/flush_utils.h b/tools/testing/selftests/powerpc/security/flush_utils.h
> index 07a5eb301466..7a3d60292916 100644
> --- a/tools/testing/selftests/powerpc/security/flush_utils.h
> +++ b/tools/testing/selftests/powerpc/security/flush_utils.h
> @@ -9,6 +9,10 @@
>  
>  #define CACHELINE_SIZE 128
>  
> +#define PERF_L1D_READ_MISS_CONFIG	((PERF_COUNT_HW_CACHE_L1D) | 		\
> +					(PERF_COUNT_HW_CACHE_OP_READ << 8) |	\
> +					(PERF_COUNT_HW_CACHE_RESULT_MISS << 16))
> +
>  void syscall_loop(char *p, unsigned long iterations,
>  		  unsigned long zero_size);
>  
> diff --git a/tools/testing/selftests/powerpc/security/rfi_flush.c b/tools/testing/selftests/powerpc/security/rfi_flush.c
> index 7565fd786640..f73484a6470f 100644
> --- a/tools/testing/selftests/powerpc/security/rfi_flush.c
> +++ b/tools/testing/selftests/powerpc/security/rfi_flush.c
> @@ -54,7 +54,7 @@ int rfi_flush_test(void)
>  
>  	rfi_flush = rfi_flush_orig;
>  
> -	fd = perf_event_open_counter(PERF_TYPE_RAW, /* L1d miss */ 0x400f0, -1);
> +	fd = perf_event_open_counter(PERF_TYPE_HW_CACHE, PERF_L1D_READ_MISS_CONFIG, -1);
>  	FAIL_IF(fd < 0);
>  
>  	p = (char *)memalign(zero_size, CACHELINE_SIZE);
> -- 
> 2.30.1

  reply	other threads:[~2021-02-24  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  7:02 [PATCH v2] selftests/powerpc: Fix L1D flushing tests for Power10 Russell Currey
2021-02-24  0:42 ` Daniel Axtens [this message]
2021-03-31  1:09 ` Michael Ellerman

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=878s7epa7s.fsf@dja-thinkpad.axtens.net \
    --to=dja@axtens.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ruscur@russell.cc \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.