From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>,
Hellstrom Thomas <thomas.hellstrom@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: [PATCH 3/5] drm/i915: More gt idling time with guc submission
Date: Sat, 29 Jan 2022 00:22:07 +0530 [thread overview]
Message-ID: <20220128185209.18077-4-ramalingam.c@intel.com> (raw)
In-Reply-To: <20220128185209.18077-1-ramalingam.c@intel.com>
On i915_selftest@live@gt_timelines, we create many contexts in loop and
create and submit request and then destoy contexts. Destroying the context
needs to disable scheduling, wait for G2H, deregister context and wait
for G2H to destroy each context. Idling of the gt has to wait for all
this to complete which is taking ~3sec for this test.
Hence we are increasing the igt_flush_test's timeout for gt idling to
3Sec.
Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
cc: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/i915/selftests/igt_flush_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/selftests/igt_flush_test.c b/drivers/gpu/drm/i915/selftests/igt_flush_test.c
index b84594601d30..b484e12df417 100644
--- a/drivers/gpu/drm/i915/selftests/igt_flush_test.c
+++ b/drivers/gpu/drm/i915/selftests/igt_flush_test.c
@@ -19,7 +19,7 @@ int igt_flush_test(struct drm_i915_private *i915)
cond_resched();
- if (intel_gt_wait_for_idle(gt, HZ) == -ETIME) {
+ if (intel_gt_wait_for_idle(gt, HZ * 3) == -ETIME) {
pr_err("%pS timed out, cancelling all further testing.\n",
__builtin_return_address(0));
--
2.20.1
next prev parent reply other threads:[~2022-01-28 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:52 [PATCH 0/5] Misc DG2 enabling patches Ramalingam C
2022-01-28 18:52 ` [PATCH 1/5] drm/i915/dg2: Add Wa_22011450934 Ramalingam C
2022-02-07 11:48 ` [Intel-gfx] " Matthew Auld
2022-02-07 11:52 ` Matthew Auld
2022-02-11 13:34 ` Ramalingam C
2022-01-28 18:52 ` [PATCH 2/5] drm/i915: align the plane_vma to min_page_size of stolen mem Ramalingam C
2022-01-31 10:18 ` Matthew Auld
2022-01-31 10:26 ` [Intel-gfx] " Matthew Auld
2022-01-28 18:52 ` Ramalingam C [this message]
2022-01-31 10:19 ` [PATCH 3/5] drm/i915: More gt idling time with guc submission Matthew Auld
2022-01-28 18:52 ` [PATCH 4/5] drm/i915/dg2: Add Wa_22011100796 Ramalingam C
2022-01-31 11:06 ` [Intel-gfx] " Matthew Auld
2022-01-28 18:52 ` [PATCH 5/5] drm/i915/guc: Allow user to override driver load failure without GuC Ramalingam C
2022-02-07 16:55 ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-02-11 13:32 ` Ramalingam C
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=20220128185209.18077-4-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@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;
as well as URLs for NNTP newsgroup(s).