Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: igt-dev@lists.freedesktop.org
Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Subject: [PATCH i-g-t v2 1/6] lib/igt_fb: fix intel modifiers for fb copying on xe driver
Date: Tue, 23 Apr 2024 17:32:41 +0300	[thread overview]
Message-ID: <20240423143246.130884-2-juhapekka.heikkila@gmail.com> (raw)
In-Reply-To: <20240423143246.130884-1-juhapekka.heikkila@gmail.com>

mc ccs need to go to vebox copy, blitter doesn't do mc ccs hence
on all platforms with ccs modifiers use engine copy for those.
Use render engine for x-tile on legacy platforms where x-tile
would otherwise endup on fastblit patch which is known to have
limitations.

Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
---
 lib/igt_fb.c | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/lib/igt_fb.c b/lib/igt_fb.c
index cc70cb91c..f6f280b13 100644
--- a/lib/igt_fb.c
+++ b/lib/igt_fb.c
@@ -2508,9 +2508,11 @@ static bool blitter_ok(const struct igt_fb *fb)
 	if (!is_intel_device(fb->fd))
 		return false;
 
-	if ((is_ccs_modifier(fb->modifier) &&
-	     !HAS_FLATCCS(intel_get_drm_devid(fb->fd))) ||
-	     is_gen12_mc_ccs_modifier(fb->modifier))
+	if ((!HAS_FLATCCS(intel_get_drm_devid(fb->fd)) &&
+	    is_ccs_modifier(fb->modifier)) ||
+	    is_gen12_mc_ccs_modifier(fb->modifier) ||
+	    (!blt_uses_extended_block_copy(fb->fd) &&
+	    fb->modifier == I915_FORMAT_MOD_X_TILED))
 		return false;
 
 	if (is_xe_device(fb->fd))
@@ -2551,6 +2553,7 @@ static bool use_enginecopy(const struct igt_fb *fb)
 		return false;
 
 	return fb->modifier == I915_FORMAT_MOD_Yf_TILED ||
+	       fb->modifier == I915_FORMAT_MOD_X_TILED ||
 	       (!HAS_FLATCCS(intel_get_drm_devid(fb->fd)) && is_ccs_modifier(fb->modifier)) ||
 	       is_gen12_mc_ccs_modifier(fb->modifier);
 }
@@ -3062,7 +3065,12 @@ static void free_linear_mapping(struct fb_blit_upload *blit)
 		igt_nouveau_delete_bo(&linear->fb);
 	} else if (is_xe_device(fd)) {
 		gem_munmap(linear->map, linear->fb.size);
-		blitcopy(fb, &linear->fb);
+
+		if (blit->ibb)
+			copy_with_engine(blit, fb, &linear->fb);
+		else
+			blitcopy(fb, &linear->fb);
+
 		gem_close(fd, linear->fb.gem_handle);
 	} else {
 		gem_munmap(linear->map, linear->fb.size);
@@ -3142,7 +3150,10 @@ static void setup_linear_mapping(struct fb_blit_upload *blit)
 
 		linear->map = igt_nouveau_mmap_bo(&linear->fb, PROT_READ | PROT_WRITE);
 	} else if (is_xe_device(fd)) {
-		blitcopy(&linear->fb, fb);
+		if (blit->ibb)
+			copy_with_engine(blit, &linear->fb, fb);
+		else
+			blitcopy(&linear->fb, fb);
 
 		linear->map = xe_bo_mmap_ext(fd, linear->fb.gem_handle,
 					     linear->fb.size, PROT_READ | PROT_WRITE);
-- 
2.25.1


  reply	other threads:[~2024-04-23 14:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 14:32 [PATCH i-g-t v2 0/6] Intel blitter framebuffer copying sanitizing Juha-Pekka Heikkila
2024-04-23 14:32 ` Juha-Pekka Heikkila [this message]
2024-04-23 14:32 ` [PATCH i-g-t v2 2/6] lib/igt_fb: make blt_compression_format function more readable Juha-Pekka Heikkila
2024-04-23 14:32 ` [PATCH i-g-t v2 3/6] lib/igt_fb: Sanitize blt_fb_init Juha-Pekka Heikkila
2024-04-23 14:32 ` [PATCH i-g-t v2 4/6] lib/igt_fb: separate intel blitter context setup from blitter function Juha-Pekka Heikkila
2024-04-23 14:32 ` [PATCH i-g-t v2 5/6] lib/igt_fb: put intel blt cleanup into its own function Juha-Pekka Heikkila
2024-04-23 14:32 ` [PATCH i-g-t v2 6/6] lib/igt_fb: unify intel blitter fb block copies between xe and i915 Juha-Pekka Heikkila
2024-04-23 15:09 ` ✗ Fi.CI.BAT: failure for Intel blitter framebuffer copying sanitizing (rev2) Patchwork
2024-04-23 15:09 ` ✓ CI.xeBAT: success " Patchwork
2024-04-23 17:10 ` ✗ Fi.CI.BAT: failure for Intel blitter framebuffer copying sanitizing (rev3) Patchwork
2024-04-23 17:12 ` ✓ CI.xeBAT: success " Patchwork
2024-04-23 19:42 ` ✗ Fi.CI.BAT: failure for Intel blitter framebuffer copying sanitizing (rev4) Patchwork
2024-04-23 20:09 ` ✗ CI.xeBAT: " Patchwork
2024-04-23 21:38 ` ✗ Fi.CI.BAT: failure for Intel blitter framebuffer copying sanitizing (rev5) Patchwork
2024-04-23 21:42 ` ✓ CI.xeBAT: success " Patchwork
2024-04-23 22:29 ` ✗ CI.xeFULL: failure for Intel blitter framebuffer copying sanitizing (rev2) Patchwork
2024-04-24  2:11 ` ✗ CI.xeFULL: failure for Intel blitter framebuffer copying sanitizing (rev3) Patchwork
2024-04-24  7:15 ` ✗ CI.xeFULL: failure for Intel blitter framebuffer copying sanitizing (rev4) Patchwork
2024-04-24  9:56 ` ✗ CI.xeFULL: failure for Intel blitter framebuffer copying sanitizing (rev5) Patchwork
2024-04-24 13:16   ` Juha-Pekka Heikkila
2024-04-25  6:59     ` Illipilli, TejasreeX
2024-04-25  6:55 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-25 14:32 ` ✗ 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=20240423143246.130884-2-juhapekka.heikkila@gmail.com \
    --to=juhapekka.heikkila@gmail.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