From: Matthew Brost <matthew.brost@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <saurabhg.gupta@intel.com>,
<lucas.demarchi@intel.com>, <john.c.harrison@intel.com>
Subject: Re: [PATCH 2/3] drm/xe/xe_guc_status: Allow lr exec queues to be banned
Date: Wed, 3 Apr 2024 03:27:35 +0000 [thread overview]
Message-ID: <ZgzMpxCvldMq7cYM@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240329184929.3675256-2-jonathan.cavitt@intel.com>
On Fri, Mar 29, 2024 at 11:49:28AM -0700, Jonathan Cavitt wrote:
> LR queues currently don't get banned during a GT/GuC reset because they
> lack a job. Though they don't have a job to detect the reset status of,
> it's still possible to tell when they should be banned by looking at the
> LRC: if the LRC head and tail don't match, then the exec queue should be
> banned and cleaned up.
>
> This also requires swapping the usage of xe_sched_tdr_queue_imm with
> xe_guc_exec_queue_trigger_cleanup, as the former is specific to non-lr
> exec queues.
>
> Suggested-by: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 294f40ab6aaf1..bc0b5ec0b2ebd 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1424,15 +1424,23 @@ static void guc_exec_queue_stop(struct xe_guc *guc, struct xe_exec_queue *q)
> */
> if (!(q->flags & (EXEC_QUEUE_FLAG_KERNEL | EXEC_QUEUE_FLAG_VM))) {
> struct xe_sched_job *job = xe_sched_first_pending_job(sched);
> + bool ban = false;
>
> if (job) {
> if ((xe_sched_job_started(job) &&
> !xe_sched_job_completed(job)) ||
> xe_sched_invalidate_job(job, 2)) {
> trace_xe_sched_job_ban(job);
> - set_exec_queue_banned(q);
> - xe_sched_tdr_queue_imm(&q->guc->sched);
> + ban = true;
> }
> + } else if (xe_exec_queue_is_lr(q) &&
> + (xe_lrc_ring_head(q->lrc) != q->lrc->ring.tail)) {
> + ban = true;
> + }
> +
> + if (ban) {
> + set_exec_queue_banned(q);
> + xe_guc_exec_queue_trigger_cleanup(q);
This coding pattern kinda bugs me but can't really think of anything better.
With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> }
> }
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-04-03 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 18:49 [PATCH 1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition Jonathan Cavitt
2024-03-29 18:49 ` [PATCH 2/3] drm/xe/xe_guc_status: Allow lr exec queues to be banned Jonathan Cavitt
2024-04-03 3:27 ` Matthew Brost [this message]
2024-03-29 18:49 ` [PATCH 3/3] drm/xe/xe_guc_submit: Declare reset if banned or killed Jonathan Cavitt
2024-04-03 3:28 ` Matthew Brost
2024-03-29 19:11 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition Patchwork
2024-03-29 19:11 ` ✓ CI.checkpatch: " Patchwork
2024-03-29 19:12 ` ✓ CI.KUnit: " Patchwork
2024-03-29 19:23 ` ✓ CI.Build: " Patchwork
2024-03-29 19:26 ` ✓ CI.Hooks: " Patchwork
2024-03-29 19:27 ` ✓ CI.checksparse: " Patchwork
2024-03-29 20:00 ` ✓ CI.BAT: " Patchwork
2024-04-03 3:19 ` [PATCH 1/3] " 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=ZgzMpxCvldMq7cYM@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@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=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