All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: hariom.pandey@intel.com
Subject: [igt-dev] [i-g-t] test/i915/basic-wide-active: set max relocation limit
Date: Wed,  7 Apr 2021 08:39:52 +0530	[thread overview]
Message-ID: <20210407030952.44288-1-tejaskumarx.surendrakumar.upadhyay@intel.com> (raw)

practically its highly unlike to get as many relocations which
basic-wide-active test is testing thus setting and adjusting
max limit and count to avoid failures on legacy platforms like KBL.

Cc: Maarten Lankhorst <maarten.lankhorst@intel.com>
Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
---
 tests/i915/gem_exec_reloc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/i915/gem_exec_reloc.c b/tests/i915/gem_exec_reloc.c
index 397c335e..a6088959 100644
--- a/tests/i915/gem_exec_reloc.c
+++ b/tests/i915/gem_exec_reloc.c
@@ -477,8 +477,8 @@ static void __wide_active(int i915, unsigned engine, unsigned long count)
 
 static void wide_active(int i915, unsigned engine)
 {
-	const uint64_t max = gem_aperture_size(i915) / 4096 / 2;
-	unsigned long count = 256;
+	const uint64_t max = 128;
+	unsigned long count = 32;
 
 	igt_until_timeout(2) {
 		uint64_t required, total;
-- 
2.30.0

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2021-04-07  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  3:09 Tejas Upadhyay [this message]
2021-04-07  4:02 ` [igt-dev] ✓ Fi.CI.BAT: success for test/i915/basic-wide-active: set max relocation limit Patchwork
2021-04-07  5:00 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-04-07  7:42 ` [igt-dev] [i-g-t] " Petri Latvala
2021-04-07  8:29   ` Surendrakumar Upadhyay, TejaskumarX

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=20210407030952.44288-1-tejaskumarx.surendrakumar.upadhyay@intel.com \
    --to=tejaskumarx.surendrakumar.upadhyay@intel.com \
    --cc=hariom.pandey@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 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.