From: John Harrison <john.c.harrison@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Invert runnable_state / pending enable check and assert
Date: Thu, 13 Jun 2024 11:23:43 -0700 [thread overview]
Message-ID: <ac2a8e03-db3c-4811-91aa-765ad79408d8@intel.com> (raw)
In-Reply-To: <20240613023452.2913247-1-matthew.brost@intel.com>
On 6/12/2024 19:34, Matthew Brost wrote:
> Rather than checking for pending enable and asserting runnable_state ==
> 1 in sched done handler, invert these. This is more robust code taking
> action based on the G2H message and asserting KMD tracking state is
> correct.
>
> Suggested-by: John Harrison <John.C.Harrison@Intel.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 74552391dc5a..373447758a60 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1782,8 +1782,8 @@ static void handle_sched_done(struct xe_guc *guc, struct xe_exec_queue *q,
> {
> trace_xe_exec_queue_scheduling_done(q);
>
> - if (exec_queue_pending_enable(q)) {
> - xe_gt_assert(guc_to_gt(guc), runnable_state == 1);
> + if (runnable_state == 1) {
> + xe_gt_assert(guc_to_gt(guc), exec_queue_pending_enable(q));
>
> q->guc->resume_time = ktime_get();
> clear_exec_queue_pending_enable(q);
next prev parent reply other threads:[~2024-06-13 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 2:34 [PATCH] drm/xe: Invert runnable_state / pending enable check and assert Matthew Brost
2024-06-13 2:39 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-06-13 18:23 ` John Harrison [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 6:13 [PATCH] " Matthew Brost
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=ac2a8e03-db3c-4811-91aa-765ad79408d8@intel.com \
--to=john.c.harrison@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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