Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI v3 14/21] drm/exec: drm_exec_trylock()
Date: Thu, 16 May 2024 20:23:32 +0200	[thread overview]
Message-ID: <20240516182339.3482-15-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20240516182339.3482-1-thomas.hellstrom@linux.intel.com>

Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
 drivers/gpu/drm/drm_exec.c | 38 ++++++++++++++++++++++++++++++++++++++
 include/drm/drm_exec.h     |  1 +
 2 files changed, 39 insertions(+)

diff --git a/drivers/gpu/drm/drm_exec.c b/drivers/gpu/drm/drm_exec.c
index 2a28cbccaec7..1a62ee24c1b8 100644
--- a/drivers/gpu/drm/drm_exec.c
+++ b/drivers/gpu/drm/drm_exec.c
@@ -207,6 +207,44 @@ int drm_exec_handle_contended(struct drm_exec *exec)
 }
 EXPORT_SYMBOL(drm_exec_handle_contended);
 
+/**
+ * drm_exec_trylock_obj - trylock a GEM object for use
+ * @exec: the drm_exec object with the state
+ * @obj: the GEM object to lock
+ *
+ * Lock a GEM object for use and grab a reference to it.
+ *
+ * Returns: -EALREADY when object is already locked (can be suppressed by
+ * setting the DRM_EXEC_IGNORE_DUPLICATES flag), -ENOMEM when memory
+ * allocation failed and zero for success.
+ */
+int drm_exec_trylock_obj(struct drm_exec *exec, struct drm_gem_object *obj)
+{
+	int ret;
+
+	might_alloc(GFP_KERNEL);
+
+	if (exec->prelocked == obj) {
+		drm_gem_object_put(exec->prelocked);
+		exec->prelocked = NULL;
+		return 0;
+	}
+
+	if (!dma_resv_trylock_ctx(obj->resv, &exec->ticket)) {
+		if (dma_resv_locking_ctx(obj->resv) == &exec->ticket)
+			return (exec->flags & DRM_EXEC_IGNORE_DUPLICATES) ? 0 : -EALREADY;
+		else
+			return -EBUSY;
+	}
+
+	ret = drm_exec_obj_locked(exec, obj);
+	if (ret)
+		dma_resv_unlock(obj->resv);
+
+	return ret;
+}
+EXPORT_SYMBOL(drm_exec_trylock_obj);
+
 /**
  * drm_exec_lock_obj - lock a GEM object for use
  * @exec: the drm_exec object with the state
diff --git a/include/drm/drm_exec.h b/include/drm/drm_exec.h
index a3490794ef35..a37c851a178b 100644
--- a/include/drm/drm_exec.h
+++ b/include/drm/drm_exec.h
@@ -148,6 +148,7 @@ void drm_exec_init(struct drm_exec *exec, u32 flags, unsigned nr);
 void drm_exec_fini(struct drm_exec *exec);
 bool drm_exec_cleanup(struct drm_exec *exec);
 int drm_exec_lock_obj(struct drm_exec *exec, struct drm_gem_object *obj);
+int drm_exec_trylock_obj(struct drm_exec *exec, struct drm_gem_object *obj);
 void drm_exec_unlock_obj(struct drm_exec *exec, struct drm_gem_object *obj);
 int drm_exec_prepare_obj(struct drm_exec *exec, struct drm_gem_object *obj,
 			 unsigned int num_fences);
-- 
2.44.0


  parent reply	other threads:[~2024-05-16 18:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 18:23 [CI v3 00/21] xe bo shrinker and exhaustive eviction Thomas Hellström
2024-05-16 18:23 ` [CI v3 01/21] drm/ttm: Allow TTM LRU list nodes of different types Thomas Hellström
2024-05-16 18:23 ` [CI v3 02/21] drm/ttm: Slightly clean up LRU list iteration Thomas Hellström
2024-05-16 18:23 ` [CI v3 03/21] drm/ttm: Use LRU hitches Thomas Hellström
2024-05-16 18:23 ` [CI v3 04/21] drm/ttm, drm/amdgpu, drm/xe: Consider hitch moves within bulk sublist moves Thomas Hellström
2024-05-16 18:23 ` [CI v3 05/21] drm/ttm: Provide a generic LRU walker helper Thomas Hellström
2024-05-16 18:23 ` [CI v3 06/21] drm/ttm: Use restartable LRU and sleeping locks for swapping Thomas Hellström
2024-05-16 18:23 ` [CI v3 07/21] drm/ttm: sleeping evict lock Thomas Hellström
2024-05-16 18:23 ` [CI v3 08/21] drm/ttm: Add a virtual base class for graphics memory backup Thomas Hellström
2024-05-16 18:23 ` [CI v3 09/21] drm/ttm/pool: Provide a helper to shrink pages Thomas Hellström
2024-05-16 18:23 ` [CI v3 10/21] drm/ttm: Use fault-injection to test error paths Thomas Hellström
2024-05-16 18:23 ` [CI v3 11/21] drm/ttm, drm/xe: Add a shrinker for xe bos Thomas Hellström
2024-05-16 18:23 ` [CI v3 12/21] dma-buf/dma-resv: Introduce dma_resv_trylock_ctx() Thomas Hellström
2024-05-16 18:23 ` [CI v3 13/21] drm/exec: Rework contended locking Thomas Hellström
2024-05-16 18:23 ` Thomas Hellström [this message]
2024-05-16 18:23 ` [CI v3 15/21] drm/exec: Add a snapshot capability Thomas Hellström
2024-05-16 18:23 ` [CI v3 16/21] drm/exec: Introduce an evict mode Thomas Hellström
2024-05-16 18:23 ` [CI v3 17/21] drm/ttm: Support drm_exec locking for eviction and swapping Thomas Hellström
2024-05-16 18:23 ` [CI v3 18/21] drm/ttm: Convert ttm vm to using drm_exec Thomas Hellström
2024-05-16 18:23 ` [CI v3 19/21] drm/xe: Use drm_exec for fault locking Thomas Hellström
2024-05-16 18:23 ` [CI v3 20/21] drm/ttm: Use drm_exec_trylock for bo initialization Thomas Hellström
2024-05-16 18:23 ` [CI v3 21/21] drm/xe: Initial support for drm exec locking during validate Thomas Hellström
2024-05-16 18:29 ` ✓ CI.Patch_applied: success for xe bo shrinker and exhaustive eviction (rev4) Patchwork
2024-05-16 18:30 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-16 18:31 ` ✓ CI.KUnit: success " Patchwork
2024-05-16 18:43 ` ✓ CI.Build: " Patchwork
2024-05-16 18:45 ` ✗ CI.Hooks: failure " Patchwork
2024-05-16 18:46 ` ✗ CI.checksparse: warning " Patchwork
2024-05-16 19:16 ` ✗ CI.BAT: 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=20240516182339.3482-15-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