From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
intel-xe@lists.freedesktop.org
Cc: Somalapuram Amaranath <Amaranath.Somalapuram@amd.com>,
Matthew Brost <matthew.brost@intel.com>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [RFC PATCH v3 15/21] drm/exec: Add a snapshot capability
Date: Wed, 22 May 2024 15:54:54 +0200 [thread overview]
Message-ID: <356482150ac036b506a1afbfe0b3cc40a0a72731.camel@linux.intel.com> (raw)
In-Reply-To: <964e2a3c-5417-40c9-b3cf-a9614881bc51@amd.com>
On Wed, 2024-05-22 at 13:27 +0200, Christian König wrote:
> Am 21.05.24 um 09:16 schrieb Thomas Hellström:
> > When validating a buffer object for submission, we might need to
> > lock
> > a number of object for eviction to make room for the validation.
> >
> > This makes it pretty likely that validation will eventually
> > succeed,
> > since eventually the validating process will hold most dma_resv
> > locks
> > of the buffer objects residing in the memory type being validated
> > for.
> >
> > However, once validation of a single object has succeeded it might
> > not
> > be beneficial to hold on to those locks anymore, and the validator
> > would want to drop the locks of all objects taken during
> > validation.
>
> Exactly avoiding that was one of the goals of developing the drm_exec
> object.
>
> When objects are unlocked after evicting them it just gives
> concurrent
> operations an opportunity to lock them and re-validate them into the
> contended domain.
>
> So why should that approach here be beneficial at all?
It's a matter of being nice to the rest of the system while *still
guaranteeing progress*. For each object we're trying to validate, we
keep on evicting other objects until we make progress even if we lock
all the objects in the domain.
If we were unlocking after each eviction, we can't really guarantee
progress.
OTOH, a concurrent locker of the object may well be one with higher
priority (lower ticket number) just wanting to perform a pagefault
So it's a tradeoff between locking just locking other processes out to
allow us to make one step of progress and to in addition hit them with
the big sledgehammer.
/Thomas
>
> Regards,
> Christian.
>
> >
> > Introduce a drm_exec snapshot functionality that can be used to
> > record the locks held at a certain time, and a restore
> > functionality
> > that restores the drm_exec state to the snapshot by dropping all
> > locks.
> >
> > Snapshots can be nested if needed.
> >
> > Cc: Christian König <christian.koenig@amd.com>
> > Cc: Somalapuram Amaranath <Amaranath.Somalapuram@amd.com>
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Cc: <dri-devel@lists.freedesktop.org>
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> > drivers/gpu/drm/drm_exec.c | 55
> > +++++++++++++++++++++++++++++++++++++-
> > include/drm/drm_exec.h | 23 +++++++++++++++-
> > 2 files changed, 76 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_exec.c
> > b/drivers/gpu/drm/drm_exec.c
> > index 1383680ffa4a..9eea5d0d3a98 100644
> > --- a/drivers/gpu/drm/drm_exec.c
> > +++ b/drivers/gpu/drm/drm_exec.c
> > @@ -57,6 +57,7 @@ static void drm_exec_unlock_all(struct drm_exec
> > *exec)
> > struct drm_gem_object *obj;
> > unsigned long index;
> >
> > + WARN_ON(exec->snap);
> > drm_exec_for_each_locked_object_reverse(exec, index, obj)
> > {
> > dma_resv_unlock(obj->resv);
> > drm_gem_object_put(obj);
> > @@ -90,6 +91,7 @@ void drm_exec_init(struct drm_exec *exec, u32
> > flags, unsigned nr)
> > exec->num_objects = 0;
> > exec->contended = DRM_EXEC_DUMMY;
> > exec->prelocked = NULL;
> > + exec->snap = NULL;
> > }
> > EXPORT_SYMBOL(drm_exec_init);
> >
> > @@ -301,7 +303,6 @@ int drm_exec_lock_obj(struct drm_exec *exec,
> > struct drm_gem_object *obj)
> > goto error_unlock;
> >
> > return 0;
> > -
> > error_unlock:
> > dma_resv_unlock(obj->resv);
> > return ret;
> > @@ -395,5 +396,57 @@ int drm_exec_prepare_array(struct drm_exec
> > *exec,
> > }
> > EXPORT_SYMBOL(drm_exec_prepare_array);
> >
> > +/**
> > + * drm_exec_restore() - Restore the drm_exec state to the point of
> > a snapshot.
> > + * @exec: The drm_exec object with the state.
> > + * @snap: The snapshot state.
> > + *
> > + * Restores the drm_exec object by means of unlocking and dropping
> > references
> > + * to objects locked after the snapshot.
> > + */
> > +void drm_exec_restore(struct drm_exec *exec, struct
> > drm_exec_snapshot *snap)
> > +{
> > + struct drm_gem_object *obj;
> > + unsigned int index;
> > +
> > + exec->snap = snap->saved_snap;
> > +
> > + drm_exec_for_each_locked_object_reverse(exec, index, obj)
> > {
> > + if (index + 1 == snap->num_locked)
> > + break;
> > +
> > + dma_resv_unlock(obj->resv);
> > + drm_gem_object_put(obj);
> > + exec->objects[index] = NULL;
> > + }
> > +
> > + exec->num_objects = snap->num_locked;
> > +
> > + if (!exec->prelocked)
> > + exec->prelocked = snap->prelocked;
> > + else
> > + drm_gem_object_put(snap->prelocked);
> > +}
> > +EXPORT_SYMBOL(drm_exec_restore);
> > +
> > +/**
> > + * drm_exec_snapshot() - Take a snapshot of the drm_exec state
> > + * @exec: The drm_exec object with the state.
> > + * @snap: The snapshot state.
> > + *
> > + * Records the @exec state in @snap. The @snap object is typically
> > allocated
> > + * in the stack of the caller.
> > + */
> > +void drm_exec_snapshot(struct drm_exec *exec, struct
> > drm_exec_snapshot *snap)
> > +{
> > + snap->num_locked = exec->num_objects;
> > + snap->prelocked = exec->prelocked;
> > + if (snap->prelocked)
> > + drm_gem_object_get(snap->prelocked);
> > + snap->saved_snap = exec->snap;
> > + exec->snap = snap;
> > +}
> > +EXPORT_SYMBOL(drm_exec_snapshot);
> > +
> > MODULE_DESCRIPTION("DRM execution context");
> > MODULE_LICENSE("Dual MIT/GPL");
> > diff --git a/include/drm/drm_exec.h b/include/drm/drm_exec.h
> > index ea0f2117ee0c..0ce4d749511b 100644
> > --- a/include/drm/drm_exec.h
> > +++ b/include/drm/drm_exec.h
> > @@ -19,7 +19,6 @@ struct drm_exec {
> > * @flags: Flags to control locking behavior
> > */
> > u32 flags;
> > -
> > /**
> > * @ticket: WW ticket used for acquiring locks
> > */
> > @@ -49,6 +48,25 @@ struct drm_exec {
> > * @prelocked: already locked GEM object due to contention
> > */
> > struct drm_gem_object *prelocked;
> > +
> > + /**
> > + * @snap: Pointer to the last snapshot taken or NULL if
> > none.
> > + */
> > + struct drm_exec_snapshot *snap;
> > +};
> > +
> > +/**
> > + * struct drm_exec_snapshot - drm_exec snapshot information
> > + */
> > +struct drm_exec_snapshot {
> > + /** @saved_snap: Pointer to the previous snapshot or NULL.
> > */
> > + struct drm_exec_snapshot *saved_snap;
> > +
> > + /** @prelocked: Refcounted pointer to the prelocked object
> > at snapshot time. */
> > + struct drm_gem_object *prelocked;
> > +
> > + /** @num_locked: Number of locked objects at snapshot
> > time. */
> > + unsigned long num_locked;
> > };
> >
> > int drm_exec_handle_contended(struct drm_exec *exec);
> > @@ -160,5 +178,8 @@ int drm_exec_prepare_array(struct drm_exec
> > *exec,
> > struct drm_gem_object **objects,
> > unsigned int num_objects,
> > unsigned int num_fences);
> > +void drm_exec_snapshot(struct drm_exec *exec, struct
> > drm_exec_snapshot *snap);
> > +void drm_exec_restore(struct drm_exec *exec, struct
> > drm_exec_snapshot *snap);
> > +
> >
> > #endif
>
next prev parent reply other threads:[~2024-05-22 13:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 7:16 [PATCH v3 00/21] TTM shrinker helpers and xe buffer object shrinker Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 01/21] drm/ttm: Allow TTM LRU list nodes of different types Thomas Hellström
2024-05-21 13:12 ` Matthew Brost
2024-05-28 9:16 ` Christian König
2024-05-21 7:16 ` [PATCH v3 02/21] drm/ttm: Slightly clean up LRU list iteration Thomas Hellström
2024-05-21 15:39 ` Matthew Brost
2024-05-28 9:19 ` Christian König
2024-05-21 7:16 ` [PATCH v3 03/21] drm/ttm: Use LRU hitches Thomas Hellström
2024-05-21 16:09 ` Matthew Brost
2024-05-21 7:16 ` [PATCH v3 04/21] drm/ttm, drm/amdgpu, drm/xe: Consider hitch moves within bulk sublist moves Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 05/21] drm/ttm: Provide a generic LRU walker helper Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 06/21] drm/ttm: Use the LRU walker helper for swapping Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 07/21] drm/ttm: Use the LRU walker for eviction Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 08/21] drm/ttm: Add a virtual base class for graphics memory backup Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 09/21] drm/ttm/pool: Provide a helper to shrink pages Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 10/21] drm/ttm: Use fault-injection to test error paths Thomas Hellström
2024-05-21 7:16 ` [PATCH v3 11/21] drm/ttm, drm/xe: Add a shrinker for xe bos Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 12/21] dma-buf/dma-resv: Introduce dma_resv_trylock_ctx() Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 13/21] drm/exec: Rework contended locking Thomas Hellström
2024-05-22 5:52 ` Christian König
2024-05-22 14:32 ` Thomas Hellström
2024-05-22 16:52 ` Christian König
2024-05-22 17:42 ` Thomas Hellström
2024-05-28 6:36 ` Thomas Hellström
2024-05-28 6:51 ` Christian König
2024-05-28 8:07 ` Thomas Hellström
2024-05-28 11:03 ` Christian König
2024-05-29 7:18 ` Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 14/21] drm/exec: Introduce a drm_exec_trylock_obj() function Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 15/21] drm/exec: Add a snapshot capability Thomas Hellström
2024-05-22 11:27 ` Christian König
2024-05-22 13:54 ` Thomas Hellström [this message]
2024-05-22 14:41 ` Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 16/21] drm/exec: Introduce an evict mode Thomas Hellström
2024-05-22 13:28 ` Christian König
2024-05-22 13:44 ` Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 17/21] drm/ttm: Support drm_exec locking for eviction and swapping Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 18/21] drm/ttm: Convert ttm vm to using drm_exec Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 19/21] drm/xe: Use drm_exec for fault locking Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 20/21] drm/ttm: Use drm_exec_trylock for bo initialization Thomas Hellström
2024-05-21 7:16 ` [RFC PATCH v3 21/21] drm/xe: Initial support for drm exec locking during validate Thomas Hellström
2024-05-21 7:22 ` [PATCH v3 00/21] TTM shrinker helpers and xe buffer object shrinker Thomas Hellström
2024-05-21 7:23 ` ✓ CI.Patch_applied: success for TTM shrinker helpers and xe buffer object shrinker (rev3) Patchwork
2024-05-21 7:24 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-21 7:25 ` ✓ CI.KUnit: success " Patchwork
2024-05-21 7:37 ` ✓ CI.Build: " Patchwork
2024-05-21 7:39 ` ✗ CI.Hooks: failure " Patchwork
2024-05-21 7:41 ` ✗ CI.checksparse: warning " Patchwork
2024-05-21 8:03 ` ✓ CI.BAT: success " Patchwork
2024-05-21 9:09 ` ✗ CI.FULL: 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=356482150ac036b506a1afbfe0b3cc40a0a72731.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=Amaranath.Somalapuram@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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