All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
Date: Thu,  3 Dec 2020 08:39:31 +0000	[thread overview]
Message-ID: <20201203083931.1370591-1-chris@chris-wilson.co.uk> (raw)

If we let an object idle in a shared GTT, it may be evicted by the
kernel in favour of another client. Thus, we have to be very careful
when asserting that two different executions of the same object will
be at the same address. If there's an idle point between the two
asserts, it will only be guaranteed to hold for full-ppgtt.

Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
---
 tests/i915/api_intel_bb.c | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
index 0cb3192cb..18814d14d 100644
--- a/tests/i915/api_intel_bb.c
+++ b/tests/i915/api_intel_bb.c
@@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
 	intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
 	check_buf(dst, COLOR_77);
 
-	poff2_src = intel_bb_get_object_offset(ibb, src->handle);
-	poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
-	igt_assert(poff_src == poff2_src);
-	igt_assert(poff_dst == poff2_dst);
+	/*
+	 * Since we let the objects idle, if the GTT is shared another client
+	 * is liable to reuse our offsets for themselves, causing us to have
+	 * to relocate. We don't expect this to happen as LRU eviction should
+	 * try to avoid reuse, but we use random eviction instead as it is
+	 * much quicker! Given that the kernel is *allowed* to relocate objects,
+	 * we cannot assert that the objects remain in the same location, unless
+	 * we are in full control of our own GTT.
+	 */
+	if (gem_uses_full_ppgtt(i915)) {
+		igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
+				  poff_src);
+		igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
+				  poff_dst);
+	}
 
 	intel_buf_destroy(src);
 	intel_buf_destroy(dst);
-- 
2.29.2

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2020-12-03  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  8:39 Chris Wilson [this message]
2020-12-03  9:26 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt Patchwork
2020-12-03 10:34 ` [Intel-gfx] [PATCH i-g-t] " Zbigniew Kempczyński
2020-12-03 10:34   ` [igt-dev] " Zbigniew Kempczyński
2020-12-03 10:51   ` [Intel-gfx] " Chris Wilson
2020-12-03 10:51     ` Chris Wilson
2020-12-03 12:26 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=20201203083931.1370591-1-chris@chris-wilson.co.uk \
    --to=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 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.