Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: "Nilawar, Badal" <badal.nilawar@intel.com>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/vm: Use xe_vm_lock() helper for locking
Date: Tue, 23 Apr 2024 17:12:24 +0000	[thread overview]
Message-ID: <Zifr+ArYb4FoGa7L@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <8379fc45-959c-409b-af57-06794782c2f8@intel.com>

On Tue, Apr 23, 2024 at 07:35:41PM +0530, Nilawar, Badal wrote:
> 
> 
> On 23-04-2024 12:33, Himal Prasad Ghimiray wrote:
> > There is no change in functionality. Using the helper function
> > defined within the driver.
> > 
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Not sure if Fixes: b06d47be7c83 ("drm/xe: Port Xe to GPUVA") need to be
> added here.

Most definitely not a fixes tag. It was correct in "Port Xe to GPUVA" to
use dma_resv_lock_interruptible as xe_vm_lock depended on VM being
fully initialized.

It wasn't until sometime later when dma-resv was moved to the GPUVM base
class this function is safe to call here.

> Otherwise looks good to me.

The patch is not complete. Replying to another message now with details.

Matt

> Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
> > ---
> >   drivers/gpu/drm/xe/xe_vm.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> > index 85d6f359142d..e9c8dc6d7b83 100644
> > --- a/drivers/gpu/drm/xe/xe_vm.c
> > +++ b/drivers/gpu/drm/xe/xe_vm.c
> > @@ -1279,7 +1279,7 @@ struct xe_vm *xe_vm_create(struct xe_device *xe, u32 flags)
> >   	drm_gem_object_put(vm_resv_obj);
> > -	err = dma_resv_lock_interruptible(xe_vm_resv(vm), NULL);
> > +	err = xe_vm_lock(vm, true);
> >   	if (err)
> >   		goto err_close;

  reply	other threads:[~2024-04-23 17:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  7:03 [PATCH] drm/xe/vm: Use xe_vm_lock() helper for locking Himal Prasad Ghimiray
2024-04-23  6:54 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-23  6:54 ` ✓ CI.checkpatch: " Patchwork
2024-04-23  6:55 ` ✓ CI.KUnit: " Patchwork
2024-04-23  7:07 ` ✓ CI.Build: " Patchwork
2024-04-23  7:10 ` ✓ CI.Hooks: " Patchwork
2024-04-23  7:11 ` ✓ CI.checksparse: " Patchwork
2024-04-23 11:59 ` ✗ CI.FULL: failure " Patchwork
2024-04-23 14:05 ` [PATCH] " Nilawar, Badal
2024-04-23 17:12   ` Matthew Brost [this message]
2024-04-23 14:58 ` ✓ CI.Patch_applied: success for drm/xe/vm: Use xe_vm_lock() helper for locking (rev2) Patchwork
2024-04-23 14:58 ` ✓ CI.checkpatch: " Patchwork
2024-04-23 14:59 ` ✓ CI.KUnit: " Patchwork
2024-04-23 15:10 ` ✓ CI.Build: " Patchwork
2024-04-23 15:13 ` ✓ CI.Hooks: " Patchwork
2024-04-23 15:21 ` [PATCH] drm/xe/vm: Use xe_vm_lock() helper for locking Dixit, Ashutosh
2024-04-23 17:16   ` Matthew Brost
2024-04-24  2:26     ` Ghimiray, Himal Prasad
2024-04-23 15:26 ` ✓ CI.checksparse: success for drm/xe/vm: Use xe_vm_lock() helper for locking (rev2) Patchwork
2024-04-23 15:59 ` ✓ CI.BAT: " Patchwork
2024-04-23 23:35 ` ✗ 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=Zifr+ArYb4FoGa7L@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=himal.prasad.ghimiray@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