Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-xe@lists.freedesktop.org>, <thomas.hellstrom@linux.intel.com>
Subject: [PATCH 12/16] fixup! drm/xe/vm: Simplify and document xe_vm_lock()
Date: Fri, 8 Dec 2023 01:46:39 -0500	[thread overview]
Message-ID: <20231208064643.877688-13-rodrigo.vivi@intel.com> (raw)
In-Reply-To: <20231208064643.877688-1-rodrigo.vivi@intel.com>

---
 drivers/gpu/drm/xe/xe_vm.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index b8e22d50d30d..795497662e18 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -3205,9 +3205,9 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
 int xe_vm_lock(struct xe_vm *vm, bool intr)
 {
 	if (intr)
-		return dma_resv_lock_interruptible(&vm->resv, NULL);
+		return dma_resv_lock_interruptible(xe_vm_resv(vm), NULL);
 
-	return dma_resv_lock(&vm->resv, NULL);
+	return dma_resv_lock(xe_vm_resv(vm), NULL);
 }
 
 /**
-- 
2.43.0


  parent reply	other threads:[~2023-12-08  6:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08  6:46 [PATCH 00/16] Adjust to GPUVM / fixup version Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 01/16] drm/gpuvm: convert WARN() to drm_WARN() variants Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 02/16] drm/gpuvm: don't always WARN in drm_gpuvm_check_overflow() Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 03/16] drm/gpuvm: export drm_gpuvm_range_valid() Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 04/16] drm/nouveau: make use of drm_gpuvm_range_valid() Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 05/16] drm/gpuvm: add common dma-resv per struct drm_gpuvm Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 06/16] drm/nouveau: make use of the GPUVM's shared dma-resv Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 07/16] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 08/16] drm/nouveau: separately allocate struct nouveau_uvmm Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 09/16] drm/gpuvm: reference count drm_gpuvm structures Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 10/16] drm/gpuvm: add an abstraction for a VM / BO combination Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 11/16] drm/gpuvm: track/lock/validate external/evicted objects Rodrigo Vivi
2023-12-08  6:46 ` Rodrigo Vivi [this message]
2023-12-08  6:46 ` [PATCH 13/16] fixup! drm/xe: Convert pagefaulting code to use drm_exec Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 14/16] fixup! drm/xe: Rework xe_exec and the VM rebind worker to use the drm_exec helper Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 15/16] fixup! drm/xe: Convert remaining instances of ttm_eu_reserve_buffers to drm_exec Rodrigo Vivi
2023-12-08  6:46 ` [PATCH 16/16] fixup! drm/xe: Port Xe to GPUVA Rodrigo Vivi
2023-12-08 10:34 ` ✓ CI.Patch_applied: success for Adjust to GPUVM / fixup version Patchwork
2023-12-08 10:35 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-08 10:36 ` ✓ CI.KUnit: success " Patchwork
2023-12-08 10:44 ` ✓ CI.Build: " Patchwork
2023-12-08 10:44 ` ✓ CI.Hooks: " Patchwork
2023-12-08 10:46 ` ✗ CI.checksparse: warning " Patchwork
2023-12-08 11:21 ` ✓ CI.BAT: success " 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=20231208064643.877688-13-rodrigo.vivi@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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