Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <matthew.d.roper@intel.com>
Subject: Re: [PATCH v4 13/18] drm/xe/multi_queue: Teardown group upon job timeout
Date: Tue, 9 Dec 2025 14:11:17 -0800	[thread overview]
Message-ID: <aTiehd7eP9dgNDtP@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20251209032055.1539229-33-niranjana.vishwanathapura@intel.com>

On Mon, Dec 08, 2025 at 07:21:03PM -0800, Niranjana Vishwanathapura wrote:
> Upon a job timeout, teardown the multi-queue group by
> triggering TDR on all queues of the multi-queue group
> and by skipping timeout checks in them.
> 
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>

Same comment as patch #9. With that:

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_exec_queue_types.h | 2 ++
>  drivers/gpu/drm/xe/xe_guc_submit.c       | 9 ++++++++-
>  2 files changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue_types.h b/drivers/gpu/drm/xe/xe_exec_queue_types.h
> index 8a954ee62505..5fc516b0bb77 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue_types.h
> +++ b/drivers/gpu/drm/xe/xe_exec_queue_types.h
> @@ -64,6 +64,8 @@ struct xe_exec_queue_group {
>  	struct mutex list_lock;
>  	/** @sync_pending: CGP_SYNC_DONE g2h response pending */
>  	bool sync_pending;
> +	/** @banned: Group banned */
> +	bool banned;
>  };
>  
>  /**
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 509433f132d0..3d6eda29a819 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -602,6 +602,8 @@ static void xe_guc_exec_queue_group_trigger_cleanup(struct xe_exec_queue *q)
>  	xe_gt_assert(guc_to_gt(exec_queue_to_guc(q)),
>  		     xe_exec_queue_is_multi_queue(q));
>  
> +	/* Group banned, skip timeout check in TDR */
> +	WRITE_ONCE(group->banned, true);
>  	xe_guc_exec_queue_trigger_cleanup(primary);
>  
>  	mutex_lock(&group->list_lock);
> @@ -1485,6 +1487,11 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
>  		exec_queue_killed_or_banned_or_wedged(q) ||
>  		exec_queue_destroyed(q);
>  
> +	/* Skip timeout check if multi-queue group is banned */
> +	if (xe_exec_queue_is_multi_queue(q) &&
> +	    READ_ONCE(q->multi_queue.group->banned))
> +		skip_timeout_check = true;
> +
>  	/*
>  	 * If devcoredump not captured and GuC capture for the job is not ready
>  	 * do manual capture first and decide later if we need to use it
> @@ -1637,7 +1644,7 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
>  	xe_sched_add_pending_job(sched, job);
>  	xe_sched_submission_start(sched);
>  
> -	xe_guc_exec_queue_trigger_cleanup(q);
> +	xe_guc_exec_queue_group_trigger_cleanup(q);
>  
>  	/* Mark all outstanding jobs as bad, thus completing them */
>  	spin_lock(&sched->base.job_list_lock);
> -- 
> 2.43.0
> 

  reply	other threads:[~2025-12-09 22:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  3:20 [PATCH v4 00/18] drm/xe: Multi Queue feature support Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 01/18] drm/xe/multi_queue: Add multi_queue_enable_mask to gt information Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 02/18] drm/xe/multi_queue: Add user interface for multi queue support Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 03/18] drm/xe/multi_queue: Add GuC " Niranjana Vishwanathapura
2025-12-09 21:17   ` Matthew Brost
2025-12-09  3:20 ` [PATCH v4 04/18] drm/xe/multi_queue: Add multi queue priority property Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 05/18] drm/xe/multi_queue: Handle invalid exec queue property setting Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 06/18] drm/xe/multi_queue: Add exec_queue set_property ioctl support Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 07/18] drm/xe/multi_queue: Add support for multi queue dynamic priority change Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 08/18] drm/xe/multi_queue: Add multi queue information to guc_info dump Niranjana Vishwanathapura
2025-12-09  3:20 ` [PATCH v4 09/18] drm/xe/multi_queue: Handle tearing down of a multi queue Niranjana Vishwanathapura
2025-12-09 22:10   ` Matthew Brost
2025-12-09  3:21 ` [PATCH v4 10/18] drm/xe/multi_queue: Set QUEUE_DRAIN_MODE for Multi Queue batches Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 11/18] drm/xe/multi_queue: Handle CGP context error Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 12/18] drm/xe/multi_queue: Reset GT upon CGP_SYNC failure Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 13/18] drm/xe/multi_queue: Teardown group upon job timeout Niranjana Vishwanathapura
2025-12-09 22:11   ` Matthew Brost [this message]
2025-12-09  3:21 ` [PATCH v4 14/18] drm/xe/multi_queue: Tracepoint support Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 15/18] drm/xe/multi_queue: Support active group after primary is destroyed Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 16/18] drm/xe/doc: Add documentation for Multi Queue Group Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 17/18] drm/xe/doc: Add documentation for Multi Queue Group GuC interface Niranjana Vishwanathapura
2025-12-09  3:21 ` [PATCH v4 18/18] drm/xe/multi_queue: Enable multi_queue on xe3p_xpc Niranjana Vishwanathapura
2025-12-09  3:30 ` ✗ CI.checkpatch: warning for drm/xe: Multi Queue feature support (rev4) Patchwork
2025-12-09  3:31 ` ✓ CI.KUnit: success " Patchwork
2025-12-09  4:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-09 11:05 ` ✗ Xe.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=aTiehd7eP9dgNDtP@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=niranjana.vishwanathapura@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