Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Xin Wang <x.wang@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Fix race between exec queue kill and VM cleanup on file close
Date: Fri, 27 Feb 2026 09:41:22 -0800	[thread overview]
Message-ID: <aaHXQv+Tzj/mNCCu@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20260227064354.531306-1-x.wang@intel.com>

On Thu, Feb 26, 2026 at 10:43:54PM -0800, Xin Wang wrote:
> During process exit, exec queues are killed asynchronously via GuC
> firmware. If VM page tables are released while the GuC is still
> processing the disable sequence, hardware can access freed memory
> causing CAT errors.
> 

Yes, I think that is fine though. The hardware can gracefully handle
IOMMU CAT errors, all this does is create a bit spam on dmesg if a user
does somethine like ctrl-c.

We still have memory protection via xe_vm_close_and_put that prevents a
GPU from corrupting memory it no longer owns after the FD closes.

Why are you thinking is a required fix?

> Fix this by reordering xe_file_close() to ensure hardware has stopped
> before releasing resources:
> 

This will cause a user ctrl-c to wait on the hardware to respond will
may be a decent amount of time which doesn't seem ideal.

> 1. Kill all exec queues (existing logic, unchanged)
> 2. Flush per-GT workqueues (ordered_wq, g2h_wq) to drain in-flight
>    GuC messages
> 3. Wait for GuC to confirm all queues are disabled via G2H feedback,
>    using wait_event_timeout on guc->ct.wq with a 5s timeout
> 4. Release queue references only after hardware confirms idle
> 5. Close and release VMs (page table teardown) last
> 
> The wait includes bail-out conditions for GuC stopped state (GT reset)
> and VF recovery, consistent with all other wait_event_timeout patterns
> in xe_guc_submit.c.
> 
> Add xe_guc_exec_queue_is_idle() to check whether a queue has been
> confirmed idle by the GuC scheduler.
> 
> Signed-off-by: Xin Wang <x.wang@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_device.c     | 67 +++++++++++++++++++++++++++++-
>  drivers/gpu/drm/xe/xe_guc_submit.c | 54 ++++++++++++++++++++++++
>  drivers/gpu/drm/xe/xe_guc_submit.h |  1 +
>  3 files changed, 121 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 3462645ca13c..e15ce3c64914 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -41,6 +41,7 @@
>  #include "xe_gt_printk.h"
>  #include "xe_gt_sriov_vf.h"
>  #include "xe_guc.h"
> +#include "xe_guc_submit.h"
>  #include "xe_guc_pc.h"
>  #include "xe_hw_engine_group.h"
>  #include "xe_hwmon.h"
> @@ -160,13 +161,29 @@ void xe_file_put(struct xe_file *xef)
>  	kref_put(&xef->refcount, xe_file_destroy);
>  }
>  
> +static bool xe_file_is_idle(struct xe_file *xef, struct xe_gt *gt)
> +{
> +	struct xe_exec_queue *q;
> +	unsigned long idx;
> +
> +	xa_for_each(&xef->exec_queue.xa, idx, q) {
> +		struct xe_exec_queue *primary = xe_exec_queue_multi_queue_primary(q);
> +		if (q->gt == gt && !xe_guc_exec_queue_is_idle(primary))

If decide to implement this xe_guc_exec_queue_is_idle would need to be
replaced with a vfunc that hooks into the GuC backend rather than
calling into the GuC backend directly.

> +			return false;
> +	}
> +
> +	return true;
> +}
> +
>  static void xe_file_close(struct drm_device *dev, struct drm_file *file)
>  {
>  	struct xe_device *xe = to_xe_device(dev);
>  	struct xe_file *xef = file->driver_priv;
>  	struct xe_vm *vm;
>  	struct xe_exec_queue *q;
> +	struct xe_gt *gt;
>  	unsigned long idx;
> +	u8 id;
>  
>  	guard(xe_pm_runtime)(xe);
>  
> @@ -175,13 +192,61 @@ static void xe_file_close(struct drm_device *dev, struct drm_file *file)
>  	 * when FD is closing as IOCTLs presumably can't be modifying the
>  	 * xarray. Taking exec_queue.lock here causes undue dependency on
>  	 * vm->lock taken during xe_exec_queue_kill().
> +	 *
> +	 * Kill all exec queues first to stop hardware execution.
> +	 * This must be done before releasing VM and page tables to avoid
> +	 * hardware memory access errors (CAT errors) during process exit.
>  	 */
>  	xa_for_each(&xef->exec_queue.xa, idx, q) {
>  		if (q->vm && q->hwe->hw_engine_group)
>  			xe_hw_engine_group_del_exec_queue(q->hwe->hw_engine_group, q);
>  		xe_exec_queue_kill(q);
> -		xe_exec_queue_put(q);
>  	}
> +
> +	/*
> +	 * Flush per-GT workqueues to drain in-flight GuC messages triggered
> +	 * by the exec queue kills above. ordered_wq handles scheduler jobs
> +	 * (H2G), and g2h_wq processes the GuC responses we're about to
> +	 * wait for.
> +	 */
> +	for_each_gt(gt, xe, id) {
> +		if (gt->ordered_wq)
> +			flush_workqueue(gt->ordered_wq);
> +		if (gt->uc.guc.ct.g2h_wq)
> +			flush_workqueue(gt->uc.guc.ct.g2h_wq);
> +	}

Likewise if we implement this the layer here would need to be cleaned
up.

Matt

> +
> +	/*
> +	 * Wait for GuC to confirm all queues are disabled. This prevents
> +	 * hardware from accessing page tables after VM cleanup.
> +	 *
> +	 * Bail out early if GuC is stopped (GT reset) or VF recovery is
> +	 * pending, as G2H confirmations cannot arrive in those states.
> +	 */
> +	smp_rmb();
> +	for_each_gt(gt, xe, id) {
> +		struct xe_guc *guc = &gt->uc.guc;
> +		long timeout = 5 * HZ;
> +		long ret;
> +
> +		ret = wait_event_timeout(guc->ct.wq,
> +					 xe_file_is_idle(xef, gt) ||
> +					 xe_guc_read_stopped(guc) ||
> +					 xe_gt_recovery_pending(gt),
> +					 timeout);
> +
> +		if (!ret && !xe_guc_read_stopped(guc) &&
> +		    !xe_gt_recovery_pending(gt))
> +			drm_warn(&xe->drm,
> +				 "Timeout waiting for queue cleanup on GT%u, CAT errors may follow\n",
> +				 id);
> +	}
> +
> +	/* Now that hardware is stopped, release the queue references */
> +	xa_for_each(&xef->exec_queue.xa, idx, q)
> +		xe_exec_queue_put(q);
> +
> +	/* Finally, close and release the VMs (clearing page tables) */
>  	xa_for_each(&xef->vm.xa, idx, vm)
>  		xe_vm_close_and_put(vm);
>  
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index ca7aa4f358d0..9d81f76bfd54 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -2792,6 +2792,60 @@ g2h_exec_queue_lookup(struct xe_guc *guc, u32 guc_id)
>  	return q;
>  }
>  
> +/**
> + * xe_guc_exec_queue_is_idle() - Check if the exec queue is truly idle on GuC
> + * @q: The exec_queue
> + *
> + * Return: True if the exec queue is no longer running on hardware, false otherwise.
> + *
> + */
> +bool xe_guc_exec_queue_is_idle(struct xe_exec_queue *q)
> +{
> +	struct xe_guc *guc = &q->gt->uc.guc;
> +	uint32_t state;
> +
> +	if (!xe_uc_fw_is_running(&guc->fw))
> +		return true;
> +
> +	state = atomic_read(&q->guc->state);
> +
> +	/*
> +	 * If queue was never enabled, it never submitted work to GuC, so
> +	 * hardware never accessed it. Safe to consider idle immediately
> +	 * without waiting for GuC cleanup, even if we later kill the queue.
> +	 */
> +	if (!(state & EXEC_QUEUE_STATE_ENABLED) &&
> +	    !(state & EXEC_QUEUE_STATE_PENDING_ENABLE))
> +		return true;
> +
> +	/*
> +	 * Queue marked for destruction during file close, or suspended (not
> +	 * executing on hardware). In both cases, the VM has been detached from
> +	 * this queue, so we can safely consider it idle. Pending GuC cleanup
> +	 * messages won't cause access issues.
> +	 */
> +	if ((state & EXEC_QUEUE_STATE_DESTROYED) || (state & EXEC_QUEUE_STATE_SUSPENDED))
> +		return true;
> +
> +	/*
> +	 * Killed queue can be idle only if no transitions are pending.
> +	 * The queue could have been killed while enable or disable was in
> +	 * progress, so we must wait for those pending transitions to complete.
> +	 */
> +	if (state & EXEC_QUEUE_STATE_KILLED)
> +		return !(state & (EXEC_QUEUE_STATE_PENDING_DISABLE |
> +			          EXEC_QUEUE_STATE_PENDING_ENABLE));
> +
> +	/*
> +	 * Queue in transitional state (pending disable but not killed).
> +	 * In the file-close path, all queues are killed above, so this return
> +	 * is not reached during normal file close. However, it's defensive
> +	 * programming: if any non-file-close caller checks is_idle without
> +	 * killing first, we correctly wait for pending_disable to clear.
> +	*/
> +	return !(state & EXEC_QUEUE_STATE_PENDING_DISABLE);
> +}
> +
>  static void deregister_exec_queue(struct xe_guc *guc, struct xe_exec_queue *q)
>  {
>  	u32 action[] = {
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.h b/drivers/gpu/drm/xe/xe_guc_submit.h
> index b3839a90c142..9fa65366edcb 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.h
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.h
> @@ -55,5 +55,6 @@ void xe_guc_register_vf_exec_queue(struct xe_exec_queue *q, int ctx_type);
>  bool xe_guc_has_registered_mlrc_queues(struct xe_guc *guc);
>  
>  int xe_guc_contexts_hwsp_rebase(struct xe_guc *guc, void *scratch);
> +bool xe_guc_exec_queue_is_idle(struct xe_exec_queue *q);
>  
>  #endif
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2026-02-27 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:43 [PATCH] drm/xe: Fix race between exec queue kill and VM cleanup on file close Xin Wang
2026-02-27  7:58 ` ✗ CI.checkpatch: warning for " Patchwork
2026-02-27  7:59 ` ✓ CI.KUnit: success " Patchwork
2026-02-27  9:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-27 16:33 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-27 17:41 ` Matthew Brost [this message]

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=aaHXQv+Tzj/mNCCu@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=x.wang@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