Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v8 02/11] drm/xe/guc_submit: Make suspend_wait interruptible
Date: Thu, 8 Aug 2024 23:51:49 +0000	[thread overview]
Message-ID: <ZrVaFfu1QvhglpYB@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240808184220.1715625-3-francois.dugast@intel.com>

On Thu, Aug 08, 2024 at 08:40:20PM +0200, Francois Dugast wrote:
> Rely on wait_event_interruptible_timeout() to put the process to sleep
> with TASK_INTERRUPTIBLE. It allows using this function in interruptible
> context.
> 
> v2: Propagate error on wait_event_interruptible_timeout (Matt Brost)
> 
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>

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

> ---
>  drivers/gpu/drm/xe/xe_guc_submit.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 460808507947..97d77fa39070 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1603,11 +1603,11 @@ static int guc_exec_queue_suspend_wait(struct xe_exec_queue *q)
>  	 * suspend_pending upon kill but to be paranoid but races in which
>  	 * suspend_pending is set after kill also check kill here.
>  	 */
> -	ret = wait_event_timeout(q->guc->suspend_wait,
> -				 !READ_ONCE(q->guc->suspend_pending) ||
> -				 exec_queue_killed(q) ||
> -				 guc_read_stopped(guc),
> -				 HZ * 5);
> +	ret = wait_event_interruptible_timeout(q->guc->suspend_wait,
> +					       !READ_ONCE(q->guc->suspend_pending) ||
> +					       exec_queue_killed(q) ||
> +					       guc_read_stopped(guc),
> +					       HZ * 5);
>  
>  	if (!ret) {
>  		xe_gt_warn(guc_to_gt(guc),
> @@ -1617,7 +1617,7 @@ static int guc_exec_queue_suspend_wait(struct xe_exec_queue *q)
>  		return -ETIME;
>  	}
>  
> -	return 0;
> +	return ret < 0 ? ret : 0;
>  }
>  
>  static void guc_exec_queue_resume(struct xe_exec_queue *q)
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-08-08 23:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 18:40 [PATCH v8 00/11] Parallel submission of dma fence jobs and LR jobs with shared hardware resources Francois Dugast
2024-08-08 18:40 ` [PATCH v8 01/11] drm/xe/hw_engine_group: Introduce xe_hw_engine_group Francois Dugast
2024-08-08 18:40 ` [PATCH v8 02/11] drm/xe/guc_submit: Make suspend_wait interruptible Francois Dugast
2024-08-08 23:51   ` Matthew Brost [this message]
2024-08-08 18:40 ` [PATCH v8 03/11] 'drm/xe/hw_engine_group: Register hw engine group's exec queues Francois Dugast
2024-08-09  3:36   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 04/11] drm/xe/hw_engine_group: Add helper to suspend faulting LR jobs Francois Dugast
2024-08-09  3:19   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 05/11] drm/xe/exec_queue: Remove duplicated code Francois Dugast
2024-08-08 18:40 ` [PATCH v8 06/11] drm/xe/exec_queue: Prepare last fence for hw engine group resume context Francois Dugast
2024-08-09  3:37   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 07/11] drm/xe/hw_engine_group: Add helper to wait for dma fence jobs Francois Dugast
2024-08-09  3:39   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 08/11] drm/xe/hw_engine_group: Ensure safe transition between execution modes Francois Dugast
2024-08-09  3:40   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 09/11] drm/xe/exec: Switch hw engine group execution mode upon job submission Francois Dugast
2024-08-09  3:57   ` Matthew Brost
2024-08-08 18:40 ` [PATCH v8 10/11] drm/xe/vm: Remove restriction that all VMs must be faulting if one is Francois Dugast
2024-08-08 18:40 ` [PATCH v8 11/11] drm/xe/device: Remove unused xe_device::usm::num_vm_in_* Francois Dugast
2024-08-08 20:57 ` ✓ CI.Patch_applied: success for Parallel submission of dma fence jobs and LR jobs with shared hardware resources (rev8) Patchwork
2024-08-08 20:58 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-08 20:59 ` ✓ CI.KUnit: success " Patchwork
2024-08-08 21:11 ` ✓ CI.Build: " Patchwork
2024-08-08 21:13 ` ✓ CI.Hooks: " Patchwork
2024-08-08 21:14 ` ✓ CI.checksparse: " Patchwork
2024-08-08 21:35 ` ✗ CI.BAT: failure " Patchwork
2024-08-09  1:29 ` ✗ CI.FULL: " 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=ZrVaFfu1QvhglpYB@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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