From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Cc: intel-xe@lists.freedesktop.org, Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH] drm/xe/vm: Use xe_vm_lock() helper for locking
Date: Tue, 23 Apr 2024 08:21:34 -0700 [thread overview]
Message-ID: <855xw8m7ep.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20240423070332.2036539-1-himal.prasad.ghimiray@intel.com>
On Tue, 23 Apr 2024 00:03:32 -0700, Himal Prasad Ghimiray wrote:
>
Hi Himal,
> 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>
> ---
> 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;
But isn't dma_resv_lock coupled with dma_resv_unlock? So that should also
be changed, if at all? And what about other places in Xe which still
contain dma_resv_lock_interruptible?
Ashutosh
next prev parent reply other threads:[~2024-04-23 15:21 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
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 ` Dixit, Ashutosh [this message]
2024-04-23 17:16 ` [PATCH] drm/xe/vm: Use xe_vm_lock() helper for locking 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=855xw8m7ep.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.