Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, jonathan.cavitt@intel.com,
	saurabhg.gupta@intel.com
Subject: [PATCH i-g-t] tests/xe_create: Reduce MAXEXECQUEUES
Date: Tue, 12 Dec 2023 11:20:50 -0800	[thread overview]
Message-ID: <20231212192050.1435986-1-jonathan.cavitt@intel.com> (raw)

FIXME: Several XE platforms are currently failing the
create-execqueue-noleak and create-execqueue-leak tests due to exceeding
the MAXTIME timeout for execution.  It appears context switching is to
blame for this issue, as enforcing execution patterns that minimze
context switches makes the test far more performant.  Unfortunately,
doing so would defeat the purpose of the test.  While a better solution
(such as reducing the number of mandatory locks and mutexes in the exec
queue creation path) is investigated, reduce MAXEXECQUEUES by half.

Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
CC: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
CC: Kamil Konieczny <kamil.konieczny@linux.intel.com>
CC: Lucas de Marchi <lucas.demarchi@intel.com>
CC: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com> 
---
 tests/intel/xe_create.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/intel/xe_create.c b/tests/intel/xe_create.c
index 1ed48a5d3e..be470944e3 100644
--- a/tests/intel/xe_create.c
+++ b/tests/intel/xe_create.c
@@ -101,7 +101,7 @@ enum exec_queue_destroy {
 	LEAK
 };
 
-#define MAXEXECQUEUES 2048
+#define MAXEXECQUEUES 1024
 #define MAXTIME 5
 
 /**
-- 
2.25.1

             reply	other threads:[~2023-12-12 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 19:20 Jonathan Cavitt [this message]
2023-12-12 20:23 ` ✓ Fi.CI.BAT: success for tests/xe_create: Reduce MAXEXECQUEUES Patchwork
2023-12-12 21:17 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-12 21:50 ` ✓ CI.xeBAT: success " 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=20231212192050.1435986-1-jonathan.cavitt@intel.com \
    --to=jonathan.cavitt@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=saurabhg.gupta@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