From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI 20/21] drm/ttm: Use drm_exec_trylock for bo initialization
Date: Wed, 15 May 2024 10:14:48 +0200 [thread overview]
Message-ID: <20240515081449.46646-21-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20240515081449.46646-1-thomas.hellstrom@linux.intel.com>
Buffer object initialization may be part of a drm_exec transaction.
Rather than using dma_resv_trylock, use drm_exec_trylock_obj().
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
drivers/gpu/drm/ttm/ttm_bo.c | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index 103a26e51792..44000c006126 100644
--- a/drivers/gpu/drm/ttm/ttm_bo.c
+++ b/drivers/gpu/drm/ttm/ttm_bo.c
@@ -919,7 +919,10 @@ int ttm_bo_init_reserved(struct ttm_device *bdev, struct ttm_buffer_object *bo,
* since otherwise lockdep will be angered in radeon.
*/
if (!resv)
- WARN_ON(!dma_resv_trylock(bo->base.resv));
+ if (ctx->exec)
+ WARN_ON(drm_exec_trylock_obj(ctx->exec, &bo->base));
+ else
+ WARN_ON(!dma_resv_trylock(bo->base.resv));
else
dma_resv_assert_held(resv);
@@ -930,8 +933,12 @@ int ttm_bo_init_reserved(struct ttm_device *bdev, struct ttm_buffer_object *bo,
return 0;
err_unlock:
- if (!resv)
- dma_resv_unlock(bo->base.resv);
+ if (!resv) {
+ if (ctx->exec)
+ drm_exec_unlock_obj(ctx->exec, &bo->base);
+ else
+ dma_resv_unlock(bo->base.resv);
+ }
err_put:
ttm_bo_put(bo);
--
2.44.0
next prev parent reply other threads:[~2024-05-15 8:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 8:14 [CI 00/21] xe bo shrinker and exhaustive eviction Thomas Hellström
2024-05-15 8:14 ` [CI 01/21] drm/ttm: Allow TTM LRU list nodes of different types Thomas Hellström
2024-05-15 8:14 ` [CI 02/21] drm/ttm: Slightly clean up LRU list iteration Thomas Hellström
2024-05-15 8:14 ` [CI 03/21] drm/ttm: Use LRU hitches Thomas Hellström
2024-05-15 8:14 ` [CI 04/21] drm/ttm, drm/amdgpu, drm/xe: Consider hitch moves within bulk sublist moves Thomas Hellström
2024-05-15 8:14 ` [CI 05/21] drm/exec: Rework contended locking Thomas Hellström
2024-05-15 8:14 ` [CI 06/21] drm/ttm: Provide a generic LRU walker helper Thomas Hellström
2024-05-15 8:14 ` [CI 07/21] drm/ttm: Use restartable LRU and sleeping locks for swapping Thomas Hellström
2024-05-15 8:14 ` [CI 08/21] drm/ttm: sleeping evict lock Thomas Hellström
2024-05-15 8:14 ` [CI 09/21] drm/ttm: Add a virtual base class for graphics memory backup Thomas Hellström
2024-05-15 8:14 ` [CI 10/21] drm/ttm/pool: Provide a helper to shrink pages Thomas Hellström
2024-05-15 8:14 ` [CI 11/21] drm/ttm: Use fault-injection to test error paths Thomas Hellström
2024-05-15 8:14 ` [CI 12/21] drm/ttm, drm/xe: Add a shrinker for xe bos Thomas Hellström
2024-05-15 8:14 ` [CI 13/21] dma-buf/dma-resv: Introduce dma_resv_trylock_ctx() Thomas Hellström
2024-05-15 8:14 ` [CI 14/21] drm/exec: drm_exec_trylock() Thomas Hellström
2024-05-15 8:14 ` [CI 15/21] drm/exec: Add a snapshot capability Thomas Hellström
2024-05-15 8:14 ` [CI 16/21] drm/exec: Introduce an evict mode Thomas Hellström
2024-05-15 8:14 ` [CI 17/21] drm/ttm: Support drm_exec locking for eviction and swapping Thomas Hellström
2024-05-15 8:14 ` [CI 18/21] drm/ttm: Convert ttm vm to using drm_exec Thomas Hellström
2024-05-15 8:14 ` [CI 19/21] drm/xe: Use drm_exec for fault locking Thomas Hellström
2024-05-15 8:14 ` Thomas Hellström [this message]
2024-05-15 8:14 ` [CI 21/21] drm/xe: Initial support for drm exec locking during validate Thomas Hellström
2024-05-15 8:20 ` ✓ CI.Patch_applied: success for xe bo shrinker and exhaustive eviction Patchwork
2024-05-15 8:21 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-15 8:22 ` ✓ CI.KUnit: success " Patchwork
2024-05-15 14:53 ` ✓ CI.Patch_applied: success for xe bo shrinker and exhaustive eviction (rev2) Patchwork
2024-05-15 14:54 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-15 14:55 ` ✓ CI.KUnit: 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=20240515081449.46646-21-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