Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
	"Natalie Vock" <natalie.vock@gmx.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Huang Rui" <ray.huang@amd.com>,
	"Matthew Auld" <matthew.auld@intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Alex Deucher" <alexander.deucher@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	 intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	 amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 01/10] drm/exec: Add helper to bypass IGNORE_DUPLICATES flag
Date: Tue, 07 Jul 2026 14:41:52 +0200	[thread overview]
Message-ID: <6fac8343dc71b1dbf17e77390cc878cfaeb6d650.camel@linux.intel.com> (raw)
In-Reply-To: <0f85e12e-7d34-40a8-9efc-0d1a00b7c24c@amd.com>

On Tue, 2026-07-07 at 14:28 +0200, Christian König wrote:
> On 7/7/26 14:09, Thomas Hellström wrote:
> > On Fri, 2026-07-03 at 18:31 +0200, Natalie Vock wrote:
> > > TTM is about to switch to drm_exec for locking objects
> > > in the LRU list. When we're done processing the object, we want
> > > to
> > > unlock it only if the caller doesn't already hold that lock. If
> > > DRM_EXEC_IGNORE_DUPLICATES is set on the exec object (which
> > > callers
> > > may
> > > require for unrelated reasons), we have no way of knowing whether
> > > the
> > > lock is already held.
> > > 
> > > To remedy this, add a separate helper that forcefully bypasses
> > > the
> > > IGNORE_DUPLICATES flag for only a single locking operation.
> > > 
> > > Signed-off-by: Natalie Vock <natalie.vock@gmx.de>
> > 
> > The first, more complete attempt to try to tackle the exhaustive
> > eviction introduced a drm_exec snapshot ability instead.
> > 
> > https://lists.freedesktop.org/archives/intel-xe/2024-May/035820.html
> > 
> > The idea was that one would want to incrementally lock more buffer
> > objects until the validation succeeded, rather than dropping each
> > single lock after processing the eviction. That's actually what
> > guarantees forward progress. Restoring the snapshot unlocked all
> > locks
> > that we grabbed in the process, and would work also for single
> > locks.
> 
> That's actually not what this patch here tries to solve.
> 
> The problem is rather since we don't remove the BOs from the LRU list
> that we try to evict some which are actually part of our working set.
> 
> So when we lock for eviction we can't ignore duplicates no matter
> what the global flag says.

Ah yes, I see that now when I've gotten to patch 9. But then I think
the commit message is a bit misleading. It talks about unlocking an
already processed object?

Thanks,
Thomas


> 
> Regards,
> Christian.
> 
> > 
> > Thanks,
> > Thomas
> > 
> > 
> > > ---
> > >  drivers/gpu/drm/drm_exec.c | 52
> > > ++++++++++++++++++++++++++++++++++--
> > > ----------
> > >  include/drm/drm_exec.h     |  2 ++
> > >  2 files changed, 41 insertions(+), 13 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/drm_exec.c
> > > b/drivers/gpu/drm/drm_exec.c
> > > index 7988f5e7d56a3..91de6b4d29df8 100644
> > > --- a/drivers/gpu/drm/drm_exec.c
> > > +++ b/drivers/gpu/drm/drm_exec.c
> > > @@ -190,18 +190,9 @@ static int drm_exec_lock_contended(struct
> > > drm_exec *exec)
> > >  	return ret;
> > >  }
> > >  
> > > -/**
> > > - * drm_exec_lock_obj - lock 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: -EDEADLK if a contention is detected, -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_lock_obj(struct drm_exec *exec, struct
> > > drm_gem_object
> > > *obj)
> > > +static int __drm_exec_lock_obj(struct drm_exec *exec,
> > > +			       struct drm_gem_object *obj,
> > > +			       bool always_report_duplicates)
> > >  {
> > >  	int ret;
> > >  
> > > @@ -226,7 +217,7 @@ int drm_exec_lock_obj(struct drm_exec *exec,
> > > struct drm_gem_object *obj)
> > >  		return -EDEADLK;
> > >  	}
> > >  
> > > -	if (unlikely(ret == -EALREADY) &&
> > > +	if (unlikely(ret == -EALREADY) &&
> > > !always_report_duplicates
> > > &&
> > >  	    exec->flags & DRM_EXEC_IGNORE_DUPLICATES)
> > >  		return 0;
> > >  
> > > @@ -243,8 +234,43 @@ int drm_exec_lock_obj(struct drm_exec *exec,
> > > struct drm_gem_object *obj)
> > >  	dma_resv_unlock(obj->resv);
> > >  	return ret;
> > >  }
> > > +
> > > +/**
> > > + * drm_exec_lock_obj - lock 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: -EDEADLK if a contention is detected, -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_lock_obj(struct drm_exec *exec, struct
> > > drm_gem_object
> > > *obj)
> > > +{
> > > +	return __drm_exec_lock_obj(exec, obj, false);
> > > +}
> > >  EXPORT_SYMBOL(drm_exec_lock_obj);
> > >  
> > > +/**
> > > + * drm_exec_lock_obj_report_dup - lock a GEM object for use, but
> > > always report duplicates
> > > + * @exec: the drm_exec object with the state
> > > + * @obj: the GEM object to lock
> > > + *
> > > + * Like drm_exec_lock_obj, lock a GEM object for use and grab a
> > > reference to it.
> > > + * Unlike drm_exec_lock_obj, DRM_EXEC_IGNORE_DUPLICATES is
> > > ignored
> > > and duplicates are
> > > + * always reported.
> > > + *
> > > + * Returns: -EDEADLK if a contention is detected, -EALREADY when
> > > object is
> > > + * already locked, -ENOMEM when memory allocation failed and
> > > zero
> > > for success.
> > > + */
> > > +int drm_exec_lock_obj_report_dup(struct drm_exec *exec,
> > > +				 struct drm_gem_object *obj)
> > > +{
> > > +	return __drm_exec_lock_obj(exec, obj, false);
> > > +}
> > > +EXPORT_SYMBOL(drm_exec_lock_obj_report_dup);
> > > +
> > >  /**
> > >   * drm_exec_unlock_obj - unlock a GEM object in this exec
> > > context
> > >   * @exec: the drm_exec object with the state
> > > diff --git a/include/drm/drm_exec.h b/include/drm/drm_exec.h
> > > index 8725ba92ff916..ff80dd2b72240 100644
> > > --- a/include/drm/drm_exec.h
> > > +++ b/include/drm/drm_exec.h
> > > @@ -176,6 +176,8 @@ 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_lock_obj_report_dup(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);

  reply	other threads:[~2026-07-07 12:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 16:31 [PATCH 00/10] Use drm_exec to lock TTM buffers, respin Natalie Vock
2026-07-03 16:31 ` [PATCH 01/10] drm/exec: Add helper to bypass IGNORE_DUPLICATES flag Natalie Vock
2026-07-06  8:43   ` Christian König
2026-07-07 12:09   ` Thomas Hellström
2026-07-07 12:28     ` Christian König
2026-07-07 12:41       ` Thomas Hellström [this message]
2026-07-07 12:54         ` Christian König
2026-07-07 13:12           ` Natalie Vock
2026-07-03 16:31 ` [PATCH 02/10] drm/ttm: replace TTMs refcount with the DRM refcount v4 Natalie Vock
2026-07-06 13:14   ` Thomas Hellström
2026-07-06 14:49     ` Christian König
2026-07-06 17:01       ` Thomas Hellström
2026-07-06 17:51         ` Matthew Brost
2026-07-06 17:53           ` Thomas Hellström
2026-07-06 18:03             ` Matthew Brost
2026-07-06 18:05               ` Matthew Brost
2026-07-07  6:30                 ` Thomas Hellström
2026-07-06 18:03           ` Thomas Hellström
2026-07-06 18:23         ` Christian König
2026-07-06 22:26           ` Dave Airlie
2026-07-07  6:56           ` Thomas Hellström
2026-07-07  7:35             ` Natalie Vock
2026-07-07  8:48             ` Christian König
2026-07-07  9:53               ` Thomas Hellström
2026-07-07 12:52                 ` Christian König
2026-07-07 14:07                   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 03/10] drm/ttm: remove ttm_lru_walk_ops Natalie Vock
2026-07-06 12:34   ` Thomas Hellström
2026-07-06 13:05     ` Christian König
2026-07-06 16:31       ` Matthew Brost
2026-07-06 13:08     ` Natalie Vock
2026-07-03 16:31 ` [PATCH 04/10] drm/ttm: grab BO reference before locking it Natalie Vock
2026-07-07 12:12   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 05/10] drm/ttm: switch to ttm_bo_lru_for_each_reserved_guarded for swapout Natalie Vock
2026-07-07 12:17   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 06/10] drm/ttm: move zombie handling into ttm_bo_evict Natalie Vock
2026-07-07 12:24   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 07/10] drm/ttm: use ttm_bo_lru_for_each_reserved_guarded in evict_all Natalie Vock
2026-07-07 12:35   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 08/10] drm/xe: remove workaround for TTM internals Natalie Vock
2026-07-07 11:52   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 09/10] drm/ttm: support using drm_exec during eviction v4 Natalie Vock
2026-07-07 12:48   ` Thomas Hellström
2026-07-03 16:31 ` [PATCH 10/10] drm/amdgpu: use drm_exec during BO validation Natalie Vock
2026-07-03 17:26 ` ✗ LGCI.VerificationFailed: failure for Use drm_exec to lock TTM buffers, respin 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=6fac8343dc71b1dbf17e77390cc878cfaeb6d650.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=mripard@kernel.org \
    --cc=natalie.vock@gmx.de \
    --cc=ray.huang@amd.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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