From: Brian Welty <brian.welty@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 1/2] drm/xe: Fix guc_exec_queue_set_priority
Date: Fri, 5 Jan 2024 11:04:39 -0800 [thread overview]
Message-ID: <20240105190440.9908-2-brian.welty@intel.com> (raw)
In-Reply-To: <20240105190440.9908-1-brian.welty@intel.com>
We need to set q->priority prior to calling guc_exec_queue_add_msg() as
that will call init_policies() and sets the scheduling properties to those
stored in the exec_queue.
Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
Signed-off-by: Brian Welty <brian.welty@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 21ac68e3246f..5de3ac47c462 100644
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c
@@ -1308,8 +1308,8 @@ static int guc_exec_queue_set_priority(struct xe_exec_queue *q,
if (!msg)
return -ENOMEM;
- guc_exec_queue_add_msg(q, msg, SET_SCHED_PROPS);
q->priority = priority;
+ guc_exec_queue_add_msg(q, msg, SET_SCHED_PROPS);
return 0;
}
--
2.43.0
next prev parent reply other threads:[~2024-01-05 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 19:04 [PATCH 0/2] Fixes for settting exec_queue priority Brian Welty
2024-01-05 19:04 ` Brian Welty [this message]
2024-01-05 19:29 ` [PATCH 1/2] drm/xe: Fix guc_exec_queue_set_priority Matthew Brost
2024-01-05 19:04 ` [PATCH 2/2] drm/xe: Fix modifying exec_queue priority in xe_migrate_init Brian Welty
2024-01-06 2:00 ` Matthew Brost
2024-01-06 0:56 ` ✓ CI.Patch_applied: success for Fixes for settting exec_queue priority Patchwork
2024-01-06 0:56 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-06 0:57 ` ✓ CI.KUnit: success " Patchwork
2024-01-06 1:05 ` ✓ CI.Build: " Patchwork
2024-01-06 1:05 ` ✓ CI.Hooks: " Patchwork
2024-01-06 1:07 ` ✓ CI.checksparse: " Patchwork
2024-01-06 1:41 ` ✓ CI.BAT: " 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=20240105190440.9908-2-brian.welty@intel.com \
--to=brian.welty@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