public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Shuicheng Lin <shuicheng.lin@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Subject: Re: [PATCH v2] drm/xe: Fix exec queue unwind on hw engine group add failure
Date: Tue, 3 Mar 2026 16:29:47 -0800	[thread overview]
Message-ID: <aad8+9SPhClAwp2H@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20260303235219.1035961-2-shuicheng.lin@intel.com>

On Tue, Mar 03, 2026 at 11:52:20PM +0000, Shuicheng Lin wrote:
> When xe_hw_engine_group_add_exec_queue() fails in
> xe_exec_queue_create_ioctl(), to undo xe_exec_queue_group_add()
> and xe_vm_add_compute_exec_queue(), the code should unwind through
> kill_exec_queue rather than directly dropping the queue reference.
> 
> Fixes: d9ec63474648 ("drm/xe/multi_queue: Add user interface for multi queue support")
> Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
> 
> ---
> Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>

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

> 
> v2: correct the jump label from delete_queue_group to kill_exec_queue (Matt)
> ---
>  drivers/gpu/drm/xe/xe_exec_queue.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
> index bb273ca02d28..4dc59f448f2e 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
> @@ -1297,7 +1297,7 @@ int xe_exec_queue_create_ioctl(struct drm_device *dev, void *data,
>  		if (q->vm && q->hwe->hw_engine_group) {
>  			err = xe_hw_engine_group_add_exec_queue(q->hwe->hw_engine_group, q);
>  			if (err)
> -				goto put_exec_queue;
> +				goto kill_exec_queue;
>  		}
>  	}
>  
> -- 
> 2.50.1
> 

  parent reply	other threads:[~2026-03-04  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 23:52 [PATCH v2] drm/xe: Fix exec queue unwind on hw engine group add failure Shuicheng Lin
2026-03-04  0:02 ` ✓ CI.KUnit: success for " Patchwork
2026-03-04  0:29 ` Matthew Brost [this message]
2026-03-04  1:13 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-04 19:12 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-05 20:27 ` ✓ CI.KUnit: success for drm/xe: Fix exec queue unwind on hw engine group add failure (rev2) Patchwork
2026-03-05 21:23 ` [PATCH v2] drm/xe: Fix exec queue unwind on hw engine group add failure Niranjana Vishwanathapura
2026-03-05 22:49   ` Lin, Shuicheng
2026-03-05 21:39 ` ✗ Xe.CI.BAT: failure for drm/xe: Fix exec queue unwind on hw engine group add failure (rev2) Patchwork
2026-03-06 13:32 ` ✗ Xe.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=aad8+9SPhClAwp2H@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=shuicheng.lin@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