From: Nirmoy Das <nirmoy.das@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: [igt-dev] [PATCH i-g-t] tests/prime_vgem: Use correct blitter
Date: Mon, 2 Oct 2023 14:14:28 +0200 [thread overview]
Message-ID: <20231002121428.3827-1-nirmoy.das@intel.com> (raw)
Use igt_blitter_copy() which picks a correct blitter
command depending on platform.
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
tests/prime_vgem.c | 52 +++++++++++++++++++++++-----------------------
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/tests/prime_vgem.c b/tests/prime_vgem.c
index 876e04ed0..551a731f5 100644
--- a/tests/prime_vgem.c
+++ b/tests/prime_vgem.c
@@ -29,7 +29,7 @@
#include "i915/gem_create.h"
#include "igt.h"
#include "igt_vgem.h"
-#include "intel_batchbuffer.h" /* igt_blitter_src_copy() */
+#include "intel_batchbuffer.h" /* igt_blitter_copy() */
/**
* TEST: prime vgem
* Description: Basic check of polling for prime/vgem fences.
@@ -351,11 +351,11 @@ static void test_fence_blt(int i915, int vgem)
write(master[1], &child, sizeof(child));
read(slave[0], &child, sizeof(child));
- igt_blitter_src_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
- I915_TILING_NONE, 0, 0, scratch.size,
- scratch.width, scratch.height, scratch.bpp,
- native, 0, scratch.pitch,
- I915_TILING_NONE, 0, 0, scratch.size);
+ igt_blitter_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
+ I915_TILING_NONE, 0, 0, scratch.size,
+ scratch.width, scratch.height, scratch.bpp,
+ native, 0, scratch.pitch,
+ I915_TILING_NONE, 0, 0, scratch.size);
gem_sync(i915, native);
for (i = 0; i < scratch.height; i++)
@@ -480,11 +480,11 @@ static void test_blt(int vgem, int i915)
ptr[scratch.pitch * i / sizeof(*ptr)] = i;
munmap(ptr, scratch.size);
- igt_blitter_src_copy(i915, ahnd, 0, NULL, native, 0, scratch.pitch,
- I915_TILING_NONE, 0, 0, scratch.size,
- scratch.width, scratch.height, scratch.bpp,
- prime, 0, scratch.pitch, I915_TILING_NONE, 0, 0,
- scratch.size);
+ igt_blitter_copy(i915, ahnd, 0, NULL, native, 0, scratch.pitch,
+ I915_TILING_NONE, 0, 0, scratch.size,
+ scratch.width, scratch.height, scratch.bpp,
+ prime, 0, scratch.pitch, I915_TILING_NONE, 0, 0,
+ scratch.size);
prime_sync_start(dmabuf, true);
prime_sync_end(dmabuf, true);
close(dmabuf);
@@ -496,11 +496,11 @@ static void test_blt(int vgem, int i915)
}
munmap(ptr, scratch.size);
- igt_blitter_src_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
- I915_TILING_NONE, 0, 0, scratch.size,
- scratch.width, scratch.height, scratch.bpp,
- native, 0, scratch.pitch, I915_TILING_NONE, 0, 0,
- scratch.size);
+ igt_blitter_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
+ I915_TILING_NONE, 0, 0, scratch.size,
+ scratch.width, scratch.height, scratch.bpp,
+ native, 0, scratch.pitch, I915_TILING_NONE, 0, 0,
+ scratch.size);
gem_sync(i915, native);
ptr = gem_mmap__device_coherent(i915, native, 0, scratch.size, PROT_READ);
@@ -620,22 +620,22 @@ static void test_blt_interleaved(int vgem, int i915)
for (i = 0; i < SLOW_QUICK(scratch.height, 64); i++) {
local[scratch.pitch * i / sizeof(*local)] = i;
- igt_blitter_src_copy(i915, ahnd, 0, NULL, native, 0,
- scratch.pitch, I915_TILING_NONE, 0, i,
- scratch.size, scratch.width, 1,
- scratch.bpp, prime, 0, scratch.pitch,
- I915_TILING_NONE, 0, i, scratch.size);
+ igt_blitter_copy(i915, ahnd, 0, NULL, native, 0,
+ scratch.pitch, I915_TILING_NONE, 0, i,
+ scratch.size, scratch.width, 1,
+ scratch.bpp, prime, 0, scratch.pitch,
+ I915_TILING_NONE, 0, i, scratch.size);
prime_sync_start(dmabuf, true);
igt_assert_eq_u32(foreign[scratch.pitch * i / sizeof(*foreign)],
i);
prime_sync_end(dmabuf, true);
foreign[scratch.pitch * i / sizeof(*foreign)] = ~i;
- igt_blitter_src_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
- I915_TILING_NONE, 0, i, scratch.size,
- scratch.width, 1,
- scratch.bpp, native, 0, scratch.pitch,
- I915_TILING_NONE, 0, i, scratch.size);
+ igt_blitter_copy(i915, ahnd, 0, NULL, prime, 0, scratch.pitch,
+ I915_TILING_NONE, 0, i, scratch.size,
+ scratch.width, 1,
+ scratch.bpp, native, 0, scratch.pitch,
+ I915_TILING_NONE, 0, i, scratch.size);
gem_sync(i915, native);
igt_assert_eq_u32(local[scratch.pitch * i / sizeof(*local)],
~i);
--
2.41.0
next reply other threads:[~2023-10-02 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 12:14 Nirmoy Das [this message]
2023-10-02 13:21 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/prime_vgem: Use correct blitter Patchwork
2023-10-02 14:33 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-10-02 16:18 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/prime_vgem: Use correct blitter (rev2) Patchwork
2023-10-02 17:17 ` [igt-dev] ✗ CI.xeBAT: " Patchwork
2023-10-05 10:37 ` [igt-dev] [PATCH i-g-t] tests/prime_vgem: Use correct blitter Nirmoy Das
2023-10-05 11:01 ` Kamil Konieczny
2023-10-06 8:59 ` Nirmoy Das
2023-10-05 18:23 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/prime_vgem: Use correct blitter (rev3) Patchwork
2023-10-05 19:32 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-10-06 12:14 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Use correct blitter (rev4) Patchwork
2023-10-06 13:39 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-07 0:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-10-09 5:22 ` [igt-dev] [PATCH i-g-t] tests/prime_vgem: Use correct blitter Sharma, Swati2
2023-10-09 13:41 ` Nirmoy Das
2023-10-09 12:12 ` Andrzej Hajda
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=20231002121428.3827-1-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=igt-dev@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