Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Resume TDR after GT reset
Date: Thu, 26 Sep 2024 19:25:22 +0200	[thread overview]
Message-ID: <3a332ca8-fef1-4cbc-b82b-c8eb1090a318@linux.intel.com> (raw)
In-Reply-To: <20240724235919.1917216-1-matthew.brost@intel.com>


On 7/25/2024 1:59 AM, Matthew Brost wrote:
> Not starting the TDR after GT reset on exec queue which have been
> restarted can lead to jobs being able to be run forever. Fix this by
> restarting the TDR.
>
> Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_gpu_scheduler.c | 5 +++++
>  drivers/gpu/drm/xe/xe_gpu_scheduler.h | 2 ++
>  drivers/gpu/drm/xe/xe_guc_submit.c    | 1 +
>  3 files changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_gpu_scheduler.c b/drivers/gpu/drm/xe/xe_gpu_scheduler.c
> index e4ad1d6ce1d5..7f24e58cc992 100644
> --- a/drivers/gpu/drm/xe/xe_gpu_scheduler.c
> +++ b/drivers/gpu/drm/xe/xe_gpu_scheduler.c
> @@ -90,6 +90,11 @@ void xe_sched_submission_stop(struct xe_gpu_scheduler *sched)
>  	cancel_work_sync(&sched->work_process_msg);
>  }
>  
> +void xe_sched_submission_resume_tdr(struct xe_gpu_scheduler *sched)
> +{
> +	drm_sched_resume_timeout(&sched->base, sched->base.timeout);
> +}
> +
>  void xe_sched_add_msg(struct xe_gpu_scheduler *sched,
>  		      struct xe_sched_msg *msg)
>  {
> diff --git a/drivers/gpu/drm/xe/xe_gpu_scheduler.h b/drivers/gpu/drm/xe/xe_gpu_scheduler.h
> index 10c6bb9c9386..6aac7fe68673 100644
> --- a/drivers/gpu/drm/xe/xe_gpu_scheduler.h
> +++ b/drivers/gpu/drm/xe/xe_gpu_scheduler.h
> @@ -22,6 +22,8 @@ void xe_sched_fini(struct xe_gpu_scheduler *sched);
>  void xe_sched_submission_start(struct xe_gpu_scheduler *sched);
>  void xe_sched_submission_stop(struct xe_gpu_scheduler *sched);
>  
> +void xe_sched_submission_resume_tdr(struct xe_gpu_scheduler *sched);
> +
>  void xe_sched_add_msg(struct xe_gpu_scheduler *sched,
>  		      struct xe_sched_msg *msg);
>  
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 460808507947..2327e11ae311 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1768,6 +1768,7 @@ static void guc_exec_queue_start(struct xe_exec_queue *q)
>  	}
>  
>  	xe_sched_submission_start(sched);
> +	xe_sched_submission_resume_tdr(sched);
>  }
>  
>  int xe_guc_submit_start(struct xe_guc *guc)

  parent reply	other threads:[~2024-09-26 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 23:59 [PATCH] drm/xe: Resume TDR after GT reset Matthew Brost
2024-07-25  0:31 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-25  0:31 ` ✓ CI.checkpatch: " Patchwork
2024-07-25  0:32 ` ✓ CI.KUnit: " Patchwork
2024-07-25  0:44 ` ✓ CI.Build: " Patchwork
2024-07-25  0:46 ` ✓ CI.Hooks: " Patchwork
2024-07-25  0:48 ` ✓ CI.checksparse: " Patchwork
2024-07-25  1:08 ` ✗ CI.BAT: failure " Patchwork
2024-07-25  2:12 ` ✗ CI.FULL: " Patchwork
2024-09-26 17:25 ` Nirmoy Das [this message]
2024-09-27  7:12   ` [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=3a332ca8-fef1-4cbc-b82b-c8eb1090a318@linux.intel.com \
    --to=nirmoy.das@linux.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