All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [CI 10/10] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm
Date: Thu, 26 Oct 2023 12:15:36 +0200	[thread overview]
Message-ID: <20231026101536.5509-10-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20231026101536.5509-1-thomas.hellstrom@linux.intel.com>

Use DRM_GPUVM_RESV_PROTECTED to relax locking.

Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.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 fa721822199a..37e98d347539 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -1243,8 +1243,8 @@ struct xe_vm *xe_vm_create(struct xe_device *xe, u32 flags)
 		goto err_no_resv;
 	}
 
-	drm_gpuvm_init(&vm->gpuvm, "Xe VM", 0, &xe->drm, vm_resv_obj,
-		       0, vm->size, 0, 0, &gpuvm_ops);
+	drm_gpuvm_init(&vm->gpuvm, "Xe VM", DRM_GPUVM_RESV_PROTECTED, &xe->drm,
+		       vm_resv_obj, 0, vm->size, 0, 0, &gpuvm_ops);
 
 	drm_gem_object_put(vm_resv_obj);
 
-- 
2.41.0


  parent reply	other threads:[~2023-10-26 10:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 10:15 [Intel-xe] [CI 01/10] drm/gpuvm: convert WARN() to drm_WARN() variants Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 02/10] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 03/10] drm/xe: Adjust to "drm/gpuvm: add common dma-resv per struct drm_gpuvm" Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 04/10] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 05/10] drm/xe: Adjust to commit "drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm" Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 06/10] drm/gpuvm: add an abstraction for a VM / BO combination Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 07/10] drm/xe: Adjust to commit "drm/gpuvm: add an abstraction for a VM/BO combination" Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 08/10] drm/gpuvm: track/lock/validate external/evicted objects Thomas Hellström
2023-10-26 10:15 ` [Intel-xe] [CI 09/10] drm/xe: Adapt to GPUVM tracking of external / evicted objects Thomas Hellström
2023-10-26 10:15 ` Thomas Hellström [this message]
2023-10-26 10:19 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,01/10] drm/gpuvm: convert WARN() to drm_WARN() variants Patchwork
2023-10-26 10:19 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-26 10:21 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-26 10:28 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-26 10:28 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-26 10:30 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-26 11:04 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-10-26 11:56 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,01/10] drm/gpuvm: convert WARN() to drm_WARN() variants (rev2) Patchwork
2023-10-26 11:57 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-26 11:58 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-26 12:05 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-26 12:05 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-26 12:07 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-26 12:41 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-10-27  8:15 [Intel-xe] [CI 01/10] drm/gpuvm: convert WARN() to drm_WARN() variants Thomas Hellström
2023-10-27  8:15 ` [Intel-xe] [CI 10/10] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-10-25 12:55 [Intel-xe] [CI 01/10] drm/gpuvm: convert WARN() to drm_WARN() variants Thomas Hellström
2023-10-25 12:55 ` [Intel-xe] [CI 10/10] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström

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=20231026101536.5509-10-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.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 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.