From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [CI 10/11] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm
Date: Tue, 31 Oct 2023 15:21:32 +0100 [thread overview]
Message-ID: <20231031142133.17129-10-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20231031142133.17129-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 5f3bdb4e48ad..6bd1f4ac462a 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -1229,8 +1229,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
next prev parent reply other threads:[~2023-10-31 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:21 [Intel-xe] [CI 01/11] drm/gpuvm: convert WARN() to drm_WARN() variants Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 02/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 03/11] drm/xe: Adjust to "drm/gpuvm: add common dma-resv per struct drm_gpuvm" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 04/11] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 05/11] drm/xe: Adjust to commit "drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 06/11] drm/gpuvm: add an abstraction for a VM / BO combination Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 07/11] drm/xe: Adjust to commit "drm/gpuvm: add an abstraction for a VM/BO combination" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 08/11] drm/gpuvm: track/lock/validate external/evicted objects Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 09/11] drm/xe: Adapt to GPUVM tracking of external / evicted objects Thomas Hellström
2023-10-31 14:21 ` Thomas Hellström [this message]
2023-10-31 14:21 ` [Intel-xe] [CI HAX 11/11] drm/xe: Disable panic_on_warn for testing purposes Thomas Hellström
2023-10-31 16:05 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,01/11] drm/gpuvm: convert WARN() to drm_WARN() variants Patchwork
2023-10-31 16:06 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-31 16:07 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-31 16:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-31 16:14 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-31 16:16 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-31 16:56 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 20:06 [Intel-xe] [CI 01/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-11 20:07 ` [Intel-xe] [CI 10/11] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-10-11 14:44 [Intel-xe] [CI 01/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-11 14:44 ` [Intel-xe] [CI 10/11] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-10-10 12:48 [Intel-xe] [CI 01/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-10 12:48 ` [Intel-xe] [CI 10/11] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-10-10 11:07 [Intel-xe] [CI 01/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-10 11:07 ` [Intel-xe] [CI 10/11] 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=20231031142133.17129-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox