From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v2] drm/xe/guc_submit: fixup deregister in job timeout
Date: Tue, 8 Aug 2023 10:19:04 +0100 [thread overview]
Message-ID: <20230808091903.114939-2-matthew.auld@intel.com> (raw)
Rather check if the engine is still registered before proceeding with
deregister steps. Also the engine being marked as disabled doesn't mean
the engine has been disabled or deregistered from GuC pov, and here we
are signalling fences so we need to be sure GuC is not still using this
context.
v2:
- Drop the read_stopped() for this path. Since we are signalling
fences on error here, best play it safe and wait for the GT reset to
mark the engine as disabled, rather than it just being queued.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/xe_guc_submit.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
index 52c61f78b083..6126ddf2fdd5 100644
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c
@@ -881,15 +881,17 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
}
/* Engine state now stable, disable scheduling if needed */
- if (exec_queue_enabled(q)) {
+ if (exec_queue_registered(q)) {
struct xe_guc *guc = exec_queue_to_guc(q);
int ret;
if (exec_queue_reset(q))
err = -EIO;
set_exec_queue_banned(q);
- xe_exec_queue_get(q);
- disable_scheduling_deregister(guc, q);
+ if (!exec_queue_destroyed(q)) {
+ xe_exec_queue_get(q);
+ disable_scheduling_deregister(guc, q);
+ }
/*
* Must wait for scheduling to be disabled before signalling
@@ -901,8 +903,8 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
*/
smp_rmb();
ret = wait_event_timeout(guc->ct.wq,
- !exec_queue_pending_disable(q) ||
- guc_read_stopped(guc), HZ * 5);
+ !exec_queue_pending_disable(q),
+ HZ * 5);
if (!ret) {
XE_WARN_ON("Schedule disable failed to respond");
sched->timeout = MIN_SCHED_TIMEOUT;
--
2.41.0
next reply other threads:[~2023-08-08 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:19 Matthew Auld [this message]
2023-08-08 11:15 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/guc_submit: fixup deregister in job timeout Patchwork
2023-08-08 11:15 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-08 11:16 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-08 11:20 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-08 11:21 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-08 11:21 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-08 13:54 ` [Intel-xe] ✓ CI.Patch_applied: success " Patchwork
2023-08-08 13:54 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-08 13:55 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-08 13:59 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-08 14:00 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-08 14:00 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-08 14:54 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-08-08 18:09 ` [Intel-xe] [PATCH v2] " Matthew Brost
2023-08-09 8:02 ` Matthew Auld
2023-08-10 14:12 ` [Intel-xe] ✗ CI.Patch_applied: 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=20230808091903.114939-2-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@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