From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH] drm/xe: Call __guc_exec_queue_fini_async direct for KERNEL exec_queues
Date: Fri, 11 Aug 2023 06:56:16 -0700 [thread overview]
Message-ID: <20230811135616.671971-1-matthew.brost@intel.com> (raw)
Usually we call __guc_exec_queue_fini_async via a worker as the
exec_queue fini can be done from within the GPU scheduler which creates
a circular dependency without a worker. Kernel exec_queues are fini'd at
driver unload (not from within the GPU scheduler) so it is safe to
directly call __guc_exec_queue_fini_async.
Reported-by: Oded Gabbay <ogabbay@kernel.org>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_guc_submit.c | 20 ++++++--------------
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
index f80cf7d7b800..a1e1f2c86912 100644
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c
@@ -956,27 +956,19 @@ static void __guc_exec_queue_fini_async(struct work_struct *w)
drm_sched_entity_fini(&ge->entity);
drm_sched_fini(&ge->sched);
- if (!(q->flags & EXEC_QUEUE_FLAG_KERNEL)) {
- kfree(ge);
- xe_exec_queue_fini(q);
- }
+ kfree(ge);
+ xe_exec_queue_fini(q);
}
static void guc_exec_queue_fini_async(struct xe_exec_queue *q)
{
- bool kernel = q->flags & EXEC_QUEUE_FLAG_KERNEL;
-
INIT_WORK(&q->guc->fini_async, __guc_exec_queue_fini_async);
- queue_work(system_wq, &q->guc->fini_async);
/* We must block on kernel engines so slabs are empty on driver unload */
- if (kernel) {
- struct xe_guc_exec_queue *ge = q->guc;
-
- flush_work(&ge->fini_async);
- kfree(ge);
- xe_exec_queue_fini(q);
- }
+ if (q->flags & EXEC_QUEUE_FLAG_KERNEL)
+ __guc_exec_queue_fini_async(&q->guc->fini_async);
+ else
+ queue_work(system_wq, &q->guc->fini_async);
}
static void __guc_exec_queue_fini(struct xe_guc *guc, struct xe_exec_queue *q)
--
2.34.1
next reply other threads:[~2023-08-11 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 13:56 Matthew Brost [this message]
2023-08-11 14:13 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Call __guc_exec_queue_fini_async direct for KERNEL exec_queues Patchwork
2023-08-11 14:13 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-11 14:14 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-11 14:18 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-11 14:18 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-11 14:19 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-11 14:56 ` [Intel-xe] ○ CI.BAT: info " 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=20230811135616.671971-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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