From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "Brost, Matthew" <matthew.brost@intel.com>,
"Harrison, John C" <john.c.harrison@intel.com>,
"Gupta, saurabhg" <saurabhg.gupta@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [PATCH v4 3/3] drm/xe/xe_guc_submit: Declare reset if banned or killed
Date: Fri, 12 Apr 2024 20:50:27 +0000 [thread overview]
Message-ID: <bb51c48274c7a6947d1b9cd356a752cae4ee110d.camel@intel.com> (raw)
In-Reply-To: <20240405175505.1161756-3-jonathan.cavitt@intel.com>
On Fri, 2024-04-05 at 10:55 -0700, Jonathan Cavitt wrote:
> Add an additional condition to the reset_status guc_exec_queue_op
> that
> returns true if the exec queue has been banned or killed. The
> reset_status op is only used for exiting any xe_wait_user_fence_ioctl
> that waits on an exec queue without timing out, so doing this will
> exit
> the ioctl early in cases where the exec queue can no longer function,
> such as after a GuC stop during a reset.
>
> Suggested-by: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Makes sense.
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 e72f2a6cad60a..d5182f66177f1 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1371,7 +1371,7 @@ static void guc_exec_queue_resume(struct
> xe_exec_queue *q)
>
> static bool guc_exec_queue_reset_status(struct xe_exec_queue *q)
> {
> - return exec_queue_reset(q);
> + return exec_queue_reset(q) || exec_queue_killed_or_banned(q);
> }
>
> /*
next prev parent reply other threads:[~2024-04-12 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 17:55 [PATCH v4 1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition Jonathan Cavitt
2024-04-05 17:55 ` [PATCH v4 2/3] drm/xe/xe_guc_submit: Allow lr exec queues to be banned Jonathan Cavitt
2024-04-12 20:48 ` Summers, Stuart
2024-04-12 20:58 ` Cavitt, Jonathan
2024-04-12 23:45 ` Matthew Brost
2024-04-15 18:20 ` Summers, Stuart
2024-04-05 17:55 ` [PATCH v4 3/3] drm/xe/xe_guc_submit: Declare reset if banned or killed Jonathan Cavitt
2024-04-09 22:56 ` Matthew Brost
2024-04-12 20:50 ` Summers, Stuart [this message]
2024-04-05 19:20 ` ✓ CI.Patch_applied: success for series starting with [v4,1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition Patchwork
2024-04-05 19:21 ` ✓ CI.checkpatch: " Patchwork
2024-04-05 19:21 ` ✓ CI.KUnit: " Patchwork
2024-04-05 19:33 ` ✓ CI.Build: " Patchwork
2024-04-05 19:35 ` ✓ CI.Hooks: " Patchwork
2024-04-05 19:37 ` ✓ CI.checksparse: " Patchwork
2024-04-05 20:07 ` ✓ CI.BAT: " Patchwork
2024-04-12 20:43 ` [PATCH v4 1/3] " Summers, Stuart
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=bb51c48274c7a6947d1b9cd356a752cae4ee110d.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.