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>,
"Vishwanathapura,
Niranjana" <niranjana.vishwanathapura@intel.com>,
"Gupta, saurabhg" <saurabhg.gupta@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>,
"Welty, Brian" <brian.welty@intel.com>
Subject: Re: [PATCH v5 3/4] drm/xe/xe_guc_submit: Allow lr exec queues to be banned
Date: Mon, 15 Apr 2024 19:24:29 +0000 [thread overview]
Message-ID: <0bbe9c140b92f01db55d08dcd8bf6c6819dacb98.camel@intel.com> (raw)
In-Reply-To: <20240415184608.2918959-3-jonathan.cavitt@intel.com>
On Mon, 2024-04-15 at 11:46 -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>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
>
> v2:
> - Fix Subject line
> - Modify change slightly to remove need for "ban" boolean
>
> v3: Revert change involving "ban" boolean to version 1
>
> v4: Add missing semicolon and remove whitespace
>
> v5: Use new xe_lrc_ring_tail function
>
> 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 7b6c033a5496b..82406637c6c5a 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1422,15 +1422,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) !=
> xe_lrc_ring_tail(q->lrc))) {
Reviewed-by: Stuart Summers <stuart.summers@intel.com>
> + ban = true;
> + }
> +
> + if (ban) {
> + set_exec_queue_banned(q);
> + xe_guc_exec_queue_trigger_cleanup(q);
> }
> }
> }
next prev parent reply other threads:[~2024-04-15 19:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 18:46 [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function definitions Jonathan Cavitt
2024-04-15 18:46 ` [PATCH v5 2/4] drm/xe/xe_guc_submit: Fix exec queue stop race condition Jonathan Cavitt
2024-04-15 18:46 ` [PATCH v5 3/4] drm/xe/xe_guc_submit: Allow lr exec queues to be banned Jonathan Cavitt
2024-04-15 19:24 ` Summers, Stuart [this message]
2024-04-15 18:46 ` [PATCH v5 4/4] drm/xe/xe_guc_submit: Declare reset if banned or killed Jonathan Cavitt
2024-04-15 19:31 ` [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function definitions Summers, Stuart
2024-04-15 19:44 ` Matthew Brost
2024-04-15 20:26 ` Cavitt, Jonathan
2024-04-15 20:29 ` Matthew Brost
2024-04-15 20:41 ` Cavitt, Jonathan
2024-04-15 22:23 ` Summers, Stuart
2024-04-15 23:16 ` ✓ CI.Patch_applied: success for series starting with [v5,1/4] " Patchwork
2024-04-15 23:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-15 23:17 ` ✓ CI.KUnit: success " Patchwork
2024-04-15 23:29 ` ✓ CI.Build: " Patchwork
2024-04-15 23:31 ` ✓ CI.Hooks: " Patchwork
2024-04-15 23:33 ` ✓ CI.checksparse: " Patchwork
2024-04-15 23:59 ` ✓ CI.BAT: " Patchwork
2024-04-16 15:54 ` ✗ CI.FULL: failure " 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=0bbe9c140b92f01db55d08dcd8bf6c6819dacb98.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=brian.welty@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=niranjana.vishwanathapura@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