Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: juha-pekka.heikkila@intel.com
Subject: [igt-dev] [PATCH 1/2] tests/intel/i915_pipe_stress: Fix create_buf function
Date: Mon, 11 Sep 2023 15:22:55 +0300	[thread overview]
Message-ID: <20230911122256.30665-2-stanislav.lisovskiy@intel.com> (raw)
In-Reply-To: <20230911122256.30665-1-stanislav.lisovskiy@intel.com>

create_buf currently does wrong assumption what it gets
width in bytes, however reality is that it gets width
in pixels, so "width/4" must be "width * 4" for bpp 32.

Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
 tests/intel/i915_pipe_stress.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/intel/i915_pipe_stress.c b/tests/intel/i915_pipe_stress.c
index 9ceb056a09..007d3a1159 100644
--- a/tests/intel/i915_pipe_stress.c
+++ b/tests/intel/i915_pipe_stress.c
@@ -201,9 +201,9 @@ create_buf(struct data *data, int width, int height, uint32_t region)
 	 * Legacy code uses 32 bpp after buffer creation.
 	 * Let's do the same due to keep shader intact.
 	 */
-	handle = gem_create_in_memory_regions(data->drm_fd, width * height, region);
+	handle = gem_create_in_memory_regions(data->drm_fd, width * 4 * height, region);
 	intel_buf_init_using_handle(data->bops, handle, buf,
-				    width/4, height, 32, 0,
+				    width * 4, height, 32, 0,
 				    I915_TILING_NONE, 0);
 
 	return buf;
-- 
2.37.3

  reply	other threads:[~2023-09-11 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:22 [igt-dev] [PATCH 0/2] i915_pipe_stress fixes Stanislav Lisovskiy
2023-09-11 12:22 ` Stanislav Lisovskiy [this message]
2023-09-11 13:25   ` [igt-dev] [PATCH 1/2] tests/intel/i915_pipe_stress: Fix create_buf function Zbigniew Kempczyński
2023-09-12 13:18   ` Stanislav Lisovskiy
2023-09-11 12:22 ` [igt-dev] [PATCH 2/2] tests/intel/i915_pipe_stress: Use only first pipe if Bigjoiner is used Stanislav Lisovskiy
2023-09-11 13:04 ` [igt-dev] ✓ CI.xeBAT: success for i915_pipe_stress fixes Patchwork
2023-09-11 13:09 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-11 16:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-12 16:02 ` [igt-dev] ✓ Fi.CI.BAT: success for i915_pipe_stress fixes (rev2) Patchwork
2023-09-12 17:18 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-12 17:37 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20230911122256.30665-2-stanislav.lisovskiy@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.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