From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jonathan.cavitt@intel.com, saurabhg.gupta@intel.com
Subject: [PATCH v7 1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition
Date: Fri, 10 May 2024 12:45:38 -0700 [thread overview]
Message-ID: <20240510194540.3246991-1-jonathan.cavitt@intel.com> (raw)
Reorder the xe_sched_tdr_queue_imm and set_exec_queue_banned calls in
guc_exec_queue_stop. This prevents a possible race condition between
the two events in which it's possible for xe_sched_tdr_queue_imm to
wake the ufence waiter before the exec queue is banned, causing the
ufence waiter to miss the banned state.
Suggested-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Stuart Summers <stuart.summers@intel.com>
---
drivers/gpu/drm/xe/xe_guc_submit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
index fde527d34f583..3a8e501f2bc25 100644
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c
@@ -1491,8 +1491,8 @@ static void guc_exec_queue_stop(struct xe_guc *guc, struct xe_exec_queue *q)
!xe_sched_job_completed(job)) ||
xe_sched_invalidate_job(job, 2)) {
trace_xe_sched_job_ban(job);
- xe_sched_tdr_queue_imm(&q->guc->sched);
set_exec_queue_banned(q);
+ xe_sched_tdr_queue_imm(&q->guc->sched);
}
}
}
--
2.25.1
next reply other threads:[~2024-05-10 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 19:45 Jonathan Cavitt [this message]
2024-05-10 19:45 ` [PATCH v7 2/3] drm/xe/xe_guc_submit: Allow lr exec queues to be banned Jonathan Cavitt
2024-05-10 19:45 ` [PATCH v7 3/3] drm/xe/xe_guc_submit: Declare reset if banned or killed or wedged Jonathan Cavitt
2024-05-10 20:05 ` ✓ CI.Patch_applied: success for series starting with [v7,1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition Patchwork
2024-05-10 20:05 ` ✓ CI.checkpatch: " Patchwork
2024-05-10 20:06 ` ✓ CI.KUnit: " Patchwork
2024-05-10 20:18 ` ✓ CI.Build: " Patchwork
2024-05-10 20:21 ` ✓ CI.Hooks: " Patchwork
2024-05-10 20:22 ` ✓ CI.checksparse: " Patchwork
2024-05-10 20:59 ` ✓ CI.BAT: " Patchwork
2024-05-11 0:09 ` ✗ CI.FULL: failure " 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=20240510194540.3246991-1-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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