public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] i915/gem_pread/pwrite: Rename "basic"
Date: Thu, 27 Jun 2019 08:18:36 +0000	[thread overview]
Message-ID: <20db22e0517c227b6fef12d7b523312fbe17c703.camel@intel.com> (raw)
In-Reply-To: <20190627073615.15573-1-chris@chris-wilson.co.uk>

On Thu, 2019-06-27 at 08:36 +0100, Chris Wilson wrote:
> The "basic" subtests perform no verification that the read/write work,
> only function as mere API exercisers and loose benchmarks. Rename them
> to reflect that they are poor benchmarks instead.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Reviewed-by: Simon Ser <simon.ser@intel.com>

> ---
>  tests/i915/gem_pread.c                | 2 +-
>  tests/i915/gem_pwrite.c               | 2 +-
>  tests/intel-ci/fast-feedback.testlist | 2 --
>  3 files changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/i915/gem_pread.c b/tests/i915/gem_pread.c
> index c64787653..0d3e10b80 100644
> --- a/tests/i915/gem_pread.c
> +++ b/tests/i915/gem_pread.c
> @@ -159,7 +159,7 @@ igt_main_args("s:", NULL, help_str, opt_handler, NULL)
>  		dst_user = malloc(object_size);
>  	}
>  
> -	igt_subtest("basic") {
> +	igt_subtest("bench") {
>  		for (count = 1; count <= 1<<17; count <<= 1) {
>  			struct timeval start, end;
>  
> diff --git a/tests/i915/gem_pwrite.c b/tests/i915/gem_pwrite.c
> index 97703a2aa..37e978791 100644
> --- a/tests/i915/gem_pwrite.c
> +++ b/tests/i915/gem_pwrite.c
> @@ -286,7 +286,7 @@ igt_main_args("s:", NULL, help_str, opt_handler, NULL)
>  		src_user = malloc(object_size);
>  	}
>  
> -	igt_subtest("basic") {
> +	igt_subtest("bench") {
>  		for (count = 1; count <= 1<<17; count <<= 1) {
>  			struct timeval start, end;
>  
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 8618dfd28..5fcb5e76d 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -87,8 +87,6 @@ igt@gem_mmap_gtt@basic-write-gtt-no-prefault
>  igt@gem_mmap_gtt@basic-write-no-prefault
>  igt@gem_mmap_gtt@basic-write-read
>  igt@gem_mmap_gtt@basic-write-read-distinct
> -igt@gem_pread@basic
> -igt@gem_pwrite@basic
>  igt@gem_render_linear_blits@basic
>  igt@gem_render_tiled_blits@basic
>  igt@gem_ringfill@basic-default
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-27  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  7:36 [igt-dev] [PATCH i-g-t] i915/gem_pread/pwrite: Rename "basic" Chris Wilson
2019-06-27  8:18 ` Ser, Simon [this message]
2019-06-27 13:26   ` [igt-dev] [Intel-gfx] " Arkadiusz Hiler
2019-06-27 13:29     ` Martin Peres
2019-06-27 10:08 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-06-28  9:44 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=20db22e0517c227b6fef12d7b523312fbe17c703.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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