Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yadav, Arvind" <arvind.yadav@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>
Subject: Re: [PATCH v3 2/2] drm/xe/migrate: fix job lock assert
Date: Thu, 20 Nov 2025 21:00:03 +0530	[thread overview]
Message-ID: <27bd7b68-078d-4c4a-9b4a-72d30356e212@intel.com> (raw)
In-Reply-To: <20251120132727.575986-6-matthew.auld@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]

Looks good to me.
Reviewed-by: Arvind Yadav <arvind.yadav@intel.com>

On 20-11-2025 18:57, Matthew Auld wrote:
> We are meant to be checking the user vm for the bind queue, but actually
> we are checking the migrate vm. For various reasons this is not
> currently firing but this will likely change in the future.
>
> Now that we have the user_vm attached to the bind queue, we can fix this
> by directly checking that here.
>
> Fixes: dba89840a920 ("drm/xe: Add GT TLB invalidation jobs")
> Signed-off-by: Matthew Auld<matthew.auld@intel.com>
> Cc: Thomas Hellström<thomas.hellstrom@linux.intel.com>
> Cc: Matthew Brost<matthew.brost@intel.com>
> Reviewed-by: Matthew Brost<matthew.brost@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_migrate.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_migrate.c b/drivers/gpu/drm/xe/xe_migrate.c
> index f3b66b55acfb..2ed8ee32b5cf 100644
> --- a/drivers/gpu/drm/xe/xe_migrate.c
> +++ b/drivers/gpu/drm/xe/xe_migrate.c
> @@ -2481,7 +2481,7 @@ void xe_migrate_job_lock(struct xe_migrate *m, struct xe_exec_queue *q)
>   	if (is_migrate)
>   		mutex_lock(&m->job_mutex);
>   	else
> -		xe_vm_assert_held(q->vm);	/* User queues VM's should be locked */
> +		xe_vm_assert_held(q->user_vm);	/* User queues VM's should be locked */
>   }
>   
>   /**
> @@ -2499,7 +2499,7 @@ void xe_migrate_job_unlock(struct xe_migrate *m, struct xe_exec_queue *q)
>   	if (is_migrate)
>   		mutex_unlock(&m->job_mutex);
>   	else
> -		xe_vm_assert_held(q->vm);	/* User queues VM's should be locked */
> +		xe_vm_assert_held(q->user_vm);	/* User queues VM's should be locked */
>   }
>   
>   #if IS_ENABLED(CONFIG_PROVE_LOCKING)

[-- Attachment #2: Type: text/html, Size: 38239 bytes --]

  reply	other threads:[~2025-11-20 15:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 13:27 [PATCH v3 0/2] Some bind queue fixes Matthew Auld
2025-11-20 13:27 ` [PATCH v3 1/2] drm/xe/uapi: disallow bind queue sharing Matthew Auld
2025-11-20 15:06   ` Matthew Brost
2025-11-20 15:47     ` Yadav, Arvind
2025-11-20 15:34   ` Lucas De Marchi
2025-11-24 13:41     ` Matthew Auld
2025-12-18 20:40       ` Matthew Brost
2025-12-19  6:36         ` Zhang, Carl
2026-01-19 12:37           ` Matthew Auld
2026-01-19 14:14             ` Mrozek, Michal
2026-01-19 15:09               ` Matthew Auld
2025-11-20 13:27 ` [PATCH v3 2/2] drm/xe/migrate: fix job lock assert Matthew Auld
2025-11-20 15:30   ` Yadav, Arvind [this message]
2025-11-20 13:52 ` ✗ CI.checkpatch: warning for Some bind queue fixes (rev3) Patchwork
2025-11-20 13:53 ` ✓ CI.KUnit: success " Patchwork
2025-11-20 14:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-20 17:38 ` ✗ 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=27bd7b68-078d-4c4a-9b4a-72d30356e212@intel.com \
    --to=arvind.yadav@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=thomas.hellstrom@linux.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