All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_big_fb: Add max HW stride length tests
Date: Thu, 24 Oct 2019 16:55:38 +0300	[thread overview]
Message-ID: <20191024135538.GA1208@intel.com> (raw)
In-Reply-To: <1571904804-2248-1-git-send-email-juhapekka.heikkila@gmail.com>

On Thu, Oct 24, 2019 at 11:13:24AM +0300, Juha-Pekka Heikkila wrote:
> Test maximum HW stride lenghts. On Intel HW up to Gen10
> maximum HW stride lenght is 32K. On Gen11 when using 64bpp
> formats strides can reach up to 64k. These test try exact
> maximum HW strides so gtt remapping will not come in play.
> 
> v2: (Ville Syrjäjä) Build new tests to run using existing code.
> 
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
>  tests/kms_big_fb.c | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++---
>  1 file changed, 68 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/kms_big_fb.c b/tests/kms_big_fb.c
> index c3498c6..de24feb 100644
> --- a/tests/kms_big_fb.c
> +++ b/tests/kms_big_fb.c
> @@ -48,6 +48,9 @@ typedef struct {
>  	igt_render_copyfunc_t render_copy;
>  	drm_intel_bufmgr *bufmgr;
>  	struct intel_batchbuffer *batch;
> +	bool max_hw_stride_test;
> +	int hw_stride;
> +	int max_hw_fb_width;
>  } data_t;
>  
>  static void init_buf(data_t *data,
> @@ -161,9 +164,6 @@ static void max_fb_size(data_t *data, int *width, int *height,
>  	uint64_t size;
>  	int i = 0;
>  
> -	*width = data->max_fb_width;
> -	*height = data->max_fb_height;
> -
>  	/* max fence stride is only 8k bytes on gen3 */
>  	if (intel_gen(data->devid) < 4 &&
>  	    format == DRM_FORMAT_XRGB8888)
> @@ -417,6 +417,14 @@ static bool test_pipe(data_t *data)
>  
>  static void test_scanout(data_t *data)
>  {
> +	if (data->max_hw_stride_test) {

This parameter seems redundant. The format/mod loop can just assign
big_fb_width/height directly.

> +		data->big_fb_width = data->max_hw_fb_width;
> +		data->big_fb_height = data->max_hw_fb_width;
> +	} else {
> +		data->big_fb_width = data->max_fb_width;
> +		data->big_fb_height = data->max_fb_height;
> +	}
> +
>  	max_fb_size(data, &data->big_fb_width, &data->big_fb_height,
>  		    data->format, data->modifier);
>  
> @@ -649,6 +657,8 @@ igt_main
>  
>  		data.bufmgr = drm_intel_bufmgr_gem_init(data.drm_fd, 4096);
>  		data.batch = intel_batchbuffer_alloc(data.bufmgr, data.devid);
> +
> +		data.max_hw_stride_test = false;
>  	}
>  
>  	/*
> @@ -704,6 +714,61 @@ igt_main
>  		}
>  	}
>  
> +	data.max_hw_stride_test = true;
> +	for (int i = 0; i < ARRAY_SIZE(modifiers); i++) {
> +		data.modifier = modifiers[i].modifier;
> +
> +		if (intel_gen(data.devid) < 11) {
> +			data.hw_stride = 32768;

That's only true for ilk+. We need to replicate i9xx_plane_max_stride()
from the kernel here. Also please move this into a nice little function
so we don't have to look at it when reading the main code. And I think
the function should just return the resulting max fb w/h and leave the
max stride/etc. as internal implementation details.

> +		} else {
> +			switch (data.modifier) {
> +			case DRM_FORMAT_MOD_LINEAR:
> +				data.hw_stride = 65536-64;
> +				break;
> +			default:
> +				data.hw_stride = 65536;
> +				break;
> +			}
> +		}
> +
> +		for (int j = 0; j < ARRAY_SIZE(formats); j++) {
> +			/*
> +			 * try only those formats which can show full lenght. 8K is
> +			 * the magic maximum pixels in Intel HW. Here 32K is used
> +			 * to have CI test results consistent for all platforms,
> +			 * 32K is smallest number possbily coming to hw_stride
> +			 * from above if{}else{}..
> +			 */
> +			if (32768 / (formats[j].bpp >> 3) > 8192)
> +				continue;
> +
> +			data.format = formats[j].format;
> +
> +			for (int k = 0; k < ARRAY_SIZE(rotations); k++) {
> +				data.rotation = rotations[k].rotation;
> +				/*
> +				 * Seems any format currently coming here will not support
> +				 * 90/270 rotations so skip those rotations.
> +				 */
> +				if (data.rotation&(IGT_ROTATION_90|IGT_ROTATION_270))
> +					continue;
> +
> +				igt_subtest_f("%s-max-hw-stride-%dbpp-rotate-%d", modifiers[i].name,
> +					      formats[j].bpp, rotations[k].angle) {
> +					data.max_hw_fb_width = data.hw_stride / (formats[j].bpp >> 3);
> +					igt_require(data.format == DRM_FORMAT_C8 ||
> +						    igt_fb_supported_format(data.format));
> +					igt_require(igt_display_has_format_mod(&data.display, data.format, data.modifier));
> +					test_scanout(&data);
> +				}
> +			}
> +
> +			igt_fixture
> +				cleanup_fb(&data);
> +		}
> +	}
> +	data.max_hw_stride_test = false;
> +
>  	igt_fixture {
>  		igt_display_fini(&data.display);
>  
> -- 
> 2.7.4
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-10-24 13:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 10:40 [igt-dev] [PATCH i-g-t] test longer than 32k strides Juha-Pekka Heikkila
2019-09-23 10:40 ` [igt-dev] [PATCH i-g-t] tests/kms_big_fb: Add over 32k HW stride tests Juha-Pekka Heikkila
2019-09-23 12:43   ` Ville Syrjälä
2019-09-27 13:43     ` Juha-Pekka Heikkila
2019-09-27 13:50       ` Ville Syrjälä
     [not found]   ` <1571904804-2248-1-git-send-email-juhapekka.heikkila@gmail.com>
2019-10-24 13:55     ` Ville Syrjälä [this message]
2019-09-23 11:41 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2019-09-23 11:45 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-09-23 13:01 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_big_fb: Add over 32k HW stride tests (rev2) Patchwork
2019-09-23 17:18 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_big_fb: Add over 32k HW stride tests Patchwork
2019-10-24  9:19 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_big_fb: Add over 32k HW stride tests (rev3) Patchwork
2019-10-24  9:35 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-10-25 10:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-03-19 18:03 [igt-dev] [PATCH i-g-t] tests/kms_big_fb: Add max HW stride length tests Juha-Pekka Heikkila
2020-03-19 19:36 Juha-Pekka Heikkila

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=20191024135538.GA1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.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 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.