mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	"Carlos Santa" <carlos.santa@intel.com>,
	"Ryan Neph" <ryanneph@google.com>,
	"Christian Koenig" <christian.koenig@amd.com>,
	"Huang Rui" <ray.huang@amd.com>,
	"Matthew Auld" <matthew.auld@intel.com>,
	"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>,
	linux-kernel@vger.kernel.org,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH v3 05/33] drm/ttm: Support defragmentation moves
Date: Fri, 20 Nov 2026 22:30:14 -0800	[thread overview]
Message-ID: <awE6dk5EYBiu8k1-@nvishwa1-desk> (raw)
In-Reply-To: <av9Yz12dG7+vtgb2@gsse-cloud1.jf.intel.com>

On Thu, Nov 19, 2026 at 12:15:11PM -0800, Matthew Brost wrote:
>On Thu, Nov 05, 2026 at 06:51:51PM -0800, Niranjana Vishwanathapura wrote:
>> On Fri, Jul 10, 2026 at 07:55:51PM -0700, Matthew Brost wrote:
>> > Add infrastructure to let a driver re-back an already-resident BO with
>> > fresh pages (e.g. at a more beneficial order) by reusing the normal move
>> > machinery.
>> >
>> > Add ctx->defrag, which makes ttm_bo_validate() skip the "current
>> > resource already compatible" short-circuit so a move is forced even when
>> > placement is unchanged. In ttm_bo_handle_move_mem(), when defragging a
>> > populated BO, stash the old tt, create and populate a fresh one
>> > (allocating new backing), and hand the old tt to the driver move
>> > callback via bo->defrag_old_tt for copying. On success the old tt is
>> > unpopulated and freed; if populate or the move fails, the freshly
>> > allocated backing is discharged and the BO is restored to its original
>> > tt and placement.
>> >
>> > The old tt is handed off through bo->defrag_old_tt (reservation-lock
>> > protected) rather than the operation context. The pointer describes BO
>> > state for the duration of the move, so keeping it on the buffer object
>> > is better layering and lets ttm_bo_move_accel_cleanup() pick it up.
>> >
>> > Because a defrag move commonly fails (beneficial-order pages are often
>> > unavailable) and then leaves the BO untouched on its original backing,
>> > defer ttm_bo_unmap_virtual() for the defrag case until the new backing
>> > has been populated and the move is about to commit. Ordinary moves still
>> > unmap up front. This avoids needlessly zapping and refaulting every
>> > userspace mapping on the common failure path where nothing moved.
>> >
>> > Teach ttm_bo_move_accel_cleanup()'s ghost path about defrag: instead of
>> > tearing the move's source tt down synchronously, hand bo->defrag_old_tt
>> > to the ghost object so it is kept populated until the copy fence signals
>> > and then unbound and destroyed asynchronously, while the BO keeps its
>> > new tt. This lets a driver pipeline defrag teardown behind the GPU copy
>> > rather than blocking on it.
>> >
>> > This is driver-opt-in and a no-op unless ctx->defrag is set.
>> >
>> > Cc: Carlos Santa <carlos.santa@intel.com>
>> > Cc: Ryan Neph <ryanneph@google.com>
>> > Cc: Christian Koenig <christian.koenig@amd.com>
>> > Cc: Huang Rui <ray.huang@amd.com>
>> > Cc: Matthew Auld <matthew.auld@intel.com>
>> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> > Cc: Maxime Ripard <mripard@kernel.org>
>> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> > Cc: David Airlie <airlied@gmail.com>
>> > Cc: Simona Vetter <simona@ffwll.ch>
>> > Cc: dri-devel@lists.freedesktop.org
>> > Cc: linux-kernel@vger.kernel.org
>> > Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> > Assisted-by: GitHub_Copilot:claude-opus-4.8
>> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
>> >
>> > ---
>> >
>> > v3:
>> > - Reject defrag moves needing a multihop bounce: WARN, restore backing,
>> >   -EINVAL (Sashiko)
>> > ---
>> > drivers/gpu/drm/ttm/ttm_bo.c      | 100 +++++++++++++++++++++++++++---
>> > drivers/gpu/drm/ttm/ttm_bo_util.c |  16 ++++-
>> > drivers/gpu/drm/ttm/ttm_pool.c    |   5 +-
>> > include/drm/ttm/ttm_bo.h          |  17 +++++
>> > 4 files changed, 127 insertions(+), 11 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
>> > index 3980f376e3ba..c1629b4c4f0f 100644
>> > --- a/drivers/gpu/drm/ttm/ttm_bo.c
>> > +++ b/drivers/gpu/drm/ttm/ttm_bo.c
>> > @@ -125,49 +125,133 @@ static int ttm_bo_handle_move_mem(struct ttm_buffer_object *bo,
>> > {
>> > 	struct ttm_device *bdev = bo->bdev;
>> > 	bool old_use_tt, new_use_tt;
>> > +	bool defrag;
>> > 	int ret;
>> >
>> > 	old_use_tt = !bo->resource || ttm_manager_type(bdev, bo->resource->mem_type)->use_tt;
>> > 	new_use_tt = ttm_manager_type(bdev, mem->mem_type)->use_tt;
>> >
>> > -	ttm_bo_unmap_virtual(bo);
>> > +	/*
>> > +	 * Only the BO that is the actual defrag target (moved in place via
>> > +	 * ttm_bo_validate(), evict == false) is being defragmented. The same
>> > +	 * ctx->defrag is threaded into evictions triggered while allocating
>> > +	 * that target's new backing (ttm_bo_evict_alloc()), so guard against
>> > +	 * an unrelated victim BO (evict == true) being misclassified as a
>> > +	 * defrag move and needlessly reallocating its backing.
>> > +	 */
>> > +	defrag = ctx->defrag && !evict && new_use_tt && bo->ttm &&
>> > +		 ttm_tt_is_populated(bo->ttm);
>> > +
>>
>> The sashiko reports a bug about '!evict' check which seems legitimate.
>>
>
>See below - we don't allow multi-hop if ctx->defrag == true - i.e., we
>pop a warning if driver tries to do this. Thus the Sashiko feedback
>isn't right.
>

I think the issue is in ttm_bo_evict():

         ret = ttm_bo_handle_move_mem(bo, evict_mem, true, ctx, &hop);
         if (ret != -EMULTIHOP)
                 break;

         ret = ttm_bo_bounce_temp_buffer(bo, ctx, &hop);

The bo here is an unrelated victim BO being evicted to make room for the defrag target's new backing —
not the BO actually being defragged. ctx is the same ctx threaded down from the defrag target's
ttm_bo_validate() call, so ctx->defrag is still set.

If the first call (evict=true) returns -EMULTIHOP, ttm_bo_bounce_temp_buffer() calls
ttm_bo_handle_move_mem(bo, hop_mem, false, ctx, NULL) — evict=false this time,
with ctx->defrag still true. defrag = ctx->defrag && !evict && ...now evaluates true for
this unrelated victim, misclassifying its bounce-completion as a defrag move.

Since this is the final hop (it's completing the bounce, not requesting another one),
it doesn't return -EMULTIHOP itself, so the WARN_ON_ONCE+EINVAL guard below never triggers
here — that guard only catches a defrag-classified move that itself needs another hop.

>> > +	/*
>> > +	 * Tear down userspace mappings up front for ordinary moves. A defrag
>> > +	 * move is likely to leave the BO in place (beneficial-order allocation
>> > +	 * commonly fails), so defer the unmap until the new backing has been
>> > +	 * populated and the move is about to commit. This avoids a needless
>> > +	 * zap and refault of every userspace mapping on the common failure,
>> > +	 * where the BO keeps its original, still-mapped backing.
>> > +	 */
>> > +	if (!defrag)
>> > +		ttm_bo_unmap_virtual(bo);
>> >
>> > 	/*
>> > 	 * Create and bind a ttm if required.
>> > 	 */
>> >
>> > 	if (new_use_tt) {
>> > +		struct ttm_tt *defrag_old_tt = NULL;
>> > +
>> > +		/*
>> > +		 * For a defrag move, stash the current populated tt and force a
>> > +		 * fresh one to be created and populated (at beneficial order).
>> > +		 * The old tt is handed to the driver move callback to copy the
>> > +		 * contents from, and freed once the move completes.
>> > +		 */
>> > +		if (defrag) {
>> > +			defrag_old_tt = bo->ttm;
>> > +			bo->ttm = NULL;
>> > +		}
>> > +
>> > 		/* Zero init the new TTM structure if the old location should
>> > 		 * have used one as well.
>> > 		 */
>> > -		ret = ttm_tt_create(bo, old_use_tt);
>> > -		if (ret)
>> > +		ret = ttm_tt_create(bo, old_use_tt && !defrag_old_tt);
>> > +		if (ret) {
>> > +			if (defrag_old_tt)
>> > +				bo->ttm = defrag_old_tt;
>> > 			goto out_err;
>> > +		}
>> >
>> > -		if (mem->mem_type != TTM_PL_SYSTEM) {
>> > +		if (defrag_old_tt || mem->mem_type != TTM_PL_SYSTEM) {
>> > 			ret = ttm_bo_populate(bo, ctx);
>> > -			if (ret)
>> > +			if (ret) {
>> > +				/*
>> > +				 * Discharge the freshly allocated backing and
>> > +				 * leave the BO on its original tt/placement.
>> > +				 */
>> > +				if (defrag_old_tt) {
>> > +					ttm_tt_destroy(bo->bdev, bo->ttm);
>> > +					bo->ttm = defrag_old_tt;
>> > +				}
>> > 				goto out_err;
>> > +			}
>> > 		}
>> > +
>> > +		bo->defrag_old_tt = defrag_old_tt;
>> > 	}
>> >
>> > 	ret = dma_resv_reserve_fences(bo->base.resv, 1);
>> > 	if (ret)
>> > 		goto out_err;
>> >
>> > +	/*
>> > +	 * A defrag move deferred its virtual unmap until the new backing was
>> > +	 * successfully populated; tear the userspace mappings down now, before
>> > +	 * the move swaps in the new pages, so the next fault re-establishes
>> > +	 * them against the new backing.
>> > +	 */
>> > +	if (defrag)
>> > +		ttm_bo_unmap_virtual(bo);
>> > +
>>
>> NIT...would it be good to always do virtual unmap here defrag or not?
>>
>
>We could unconditionally move the ttm_bo_unmap_virtual here. I didn't do
>that to not mess non-defrag behavior but it looks harmless to
>unconditionally shuffle around.

yes, ok.

>
>> > 	ret = bdev->funcs->move(bo, evict, ctx, mem, hop);
>>
>> Sashiko reports a bug here when ttm_bo_move_memcpy() is used as move()
>> function. Though xe doesn't use that function, it is perhaps good to
>> guard against.
>>
>
>What is suggestion to guard against this?
>

As ttm_bo_move_memcpy() is not defragmentation aware, it will cause both
source and destination kmap to refer to same bo->ttm. we should probably
guard against drivers falling back on ttm_bo_move_memcpy(). May be in
ttm_bo_move_memcpy(), add a WARN_ON if bo->defrag_old_tt is set and
return error?

>> > 	if (ret) {
>> > -		if (ret == -EMULTIHOP)
>> > +		if (ret == -EMULTIHOP) {
>> > +			/*
>> > +			 * A defrag move targets the BO's current placement and
>> > +			 * must complete in a single hop. A driver requesting a
>> > +			 * bounce here is unsupported: restore the original
>> > +			 * backing and fail the defrag rather than retrying the
>> > +			 * multihop with ctx->defrag still set, which would
>> > +			 * misclassify the bounce as another defrag move and
>> > +			 * overwrite/leak bo->defrag_old_tt.
>> > +			 */
>> > +			if (unlikely(defrag)) {
>
>Here is what makes -EMULTIHOP (Sashiko evict issue) impossible.
>

Responded above.

>> > +				WARN_ON_ONCE(1);
>> > +				ret = -EINVAL;
>> > +				goto out_err;
>> > +			}
>> > 			return ret;
>> > +		}
>> > 		goto out_err;
>> > 	}
>> >
>> > +	if (bo->defrag_old_tt) {
>> > +		ttm_tt_unpopulate(bo->bdev, bo->defrag_old_tt);
>> > +		ttm_tt_destroy(bo->bdev, bo->defrag_old_tt);
>> > +		bo->defrag_old_tt = NULL;
>> > +	}
>> > +
>> > 	ctx->bytes_moved += bo->base.size;
>> > 	return 0;
>> >
>> > out_err:
>> > -	if (!old_use_tt)
>> > +	if (bo->defrag_old_tt) {
>> > +		/* Failed defrag move: restore the original backing. */
>> > +		ttm_bo_tt_destroy(bo);
>> > +		bo->ttm = bo->defrag_old_tt;
>> > +		bo->defrag_old_tt = NULL;
>> > +	} else if (!old_use_tt) {
>>
>> Another sashiko reported bug about tearing down the old pages while an
>> async copy is still in progress. Looks like xe driver waits for move to
>> complete before returning, so should be fine. But probably worth adding
>> a documentation for defrag_old_tt that "a defrag-aware move callback must
>> not return an error while a copy into the new backing is still in flight
>>
>
>I think it is implied in the ->move() contract if one fails after
>triggering an async move, you must wait on async move before returning
>or TTM will explode. This appears to be existing behavior too.
>

Ok.

One more point below.

>Matt
>
>> Niranjana
>>
>> > 		ttm_bo_tt_destroy(bo);
>> > +	}
>> >
>> > 	return ret;
>> > }
>> > @@ -835,7 +919,7 @@ int ttm_bo_validate(struct ttm_buffer_object *bo,
>> > 	force_space = false;
>> > 	do {
>> > 		/* Check whether we need to move buffer. */
>> > -		if (bo->resource &&
>> > +		if (bo->resource && !ctx->defrag &&
>> > 		    ttm_resource_compatible(bo->resource, placement,
>> > 					    force_space))
>> > 			return 0;
>> > diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c b/drivers/gpu/drm/ttm/ttm_bo_util.c
>> > index 3e3c201a0222..771313162c8d 100644
>> > --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
>> > +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
>> > @@ -626,10 +626,22 @@ static int ttm_bo_move_to_ghost(struct ttm_buffer_object *bo,
>> > 	 * bo to be unbound and destroyed.
>> > 	 */
>> >
>> > -	if (dst_use_tt)
>> > +	if (bo->defrag_old_tt) {
>> > +		/*
>> > +		 * Defrag move: @bo already points at the freshly allocated,
>> > +		 * beneficial-order tt that the move copied into. Hand the old
>> > +		 * tt (the move's source) to the ghost so it is kept populated
>> > +		 * until @fence signals and then unbound and destroyed, instead
>> > +		 * of being torn down synchronously. @bo keeps its new tt.
>> > +		 */
>> > +		ghost_obj->ttm = bo->defrag_old_tt;
>> > +		ghost_obj->defrag_old_tt = NULL;
>> > +		bo->defrag_old_tt = NULL;
>> > +	} else if (dst_use_tt) {
>> > 		ghost_obj->ttm = NULL;
>> > -	else
>> > +	} else {
>> > 		bo->ttm = NULL;
>> > +	}
>> >
>> > 	dma_resv_unlock(&ghost_obj->base._resv);
>> > 	ttm_bo_put(ghost_obj);
>> > diff --git a/drivers/gpu/drm/ttm/ttm_pool.c b/drivers/gpu/drm/ttm/ttm_pool.c
>> > index 0ca63f5ce73c..d045105afc24 100644
>> > --- a/drivers/gpu/drm/ttm/ttm_pool.c
>> > +++ b/drivers/gpu/drm/ttm/ttm_pool.c
>> > @@ -860,8 +860,11 @@ static int ttm_pool_iter_lower_order(struct ttm_pool_alloc_iter *it)
>> > 	 * pages. Record it so the driver can later try to defragment the object
>> > 	 * back to beneficial order.
>> > 	 */
>> > -	if (it->beneficial_order && it->order == it->beneficial_order)
>> > +	if (it->beneficial_order && it->order == it->beneficial_order) {
>> > 		it->tt->page_flags |= TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED;
>> > +		if (it->ctx->defrag)
>> > +			return -ENOMEM;
>> > +	}
>>
>> NIT...probably good to add a comment here that says something like,
>> 'return error here as the purpose of defragmentation is to get beneficial order'.
>>

I guess, you missed this point (sorry for signing early at previous comment).

Niranjana

>> >
>> > 	it->order--;
>> > 	it->page_caching = it->tt->caching;
>> > diff --git a/include/drm/ttm/ttm_bo.h b/include/drm/ttm/ttm_bo.h
>> > index fd814b5cf535..f4f8a8c29f04 100644
>> > --- a/include/drm/ttm/ttm_bo.h
>> > +++ b/include/drm/ttm/ttm_bo.h
>> > @@ -135,6 +135,16 @@ struct ttm_buffer_object {
>> > 	 * reservation lock.
>> > 	 */
>> > 	struct sg_table *sg;
>> > +
>> > +	/**
>> > +	 * @defrag_old_tt: Used internally during a defrag move to hand the BO's
>> > +	 * previous, populated struct ttm_tt to the driver's move callback so
>> > +	 * that it can copy the contents into the freshly allocated
>> > +	 * beneficial-order backing. Set by TTM, consumed by the driver; the old
>> > +	 * tt is freed (or restored on failure) by TTM once the move completes.
>> > +	 * Protected by the reservation lock.
>> > +	 */
>> > +	struct ttm_tt *defrag_old_tt;
>> > };
>> >
>> > #define TTM_BO_MAP_IOMEM_MASK 0x80
>> > @@ -194,6 +204,13 @@ struct ttm_operation_ctx {
>> > 	 * reclaim/compaction before falling back to a smaller order anyway.
>> > 	 */
>> > 	bool beneficial_reclaim_backoff;
>> > +	/**
>> > +	 * @defrag: Defragmentation pass. Attempt a move even when the bo's
>> > +	 * current resource is already compatible with the requested placement,
>> > +	 * so that the backing store can be reallocated at the pool's beneficial
>> > +	 * order.
>> > +	 */
>> > +	bool defrag;
>> > 	/**
>> > 	 * @resv: Reservation object to be used together with
>> > 	 * @allow_res_evict.
>> > --
>> > 2.34.1
>> >

  reply	other threads:[~2026-11-21  6:30 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  2:55 [PATCH v3 00/33] drm/ttm, drm/xe: Minimize dma-resv hold times and defragment sub-optimally backed BOs Matthew Brost
2026-07-11  2:55 ` [PATCH v3 01/33] drm/ttm/pool: Allow backing off reclaim at the beneficial order Matthew Brost
2026-11-06  2:55   ` Niranjana Vishwanathapura
2026-11-19 18:47     ` Matthew Brost
2026-07-11  2:55 ` [PATCH v3 02/33] drm/ttm/pool: Add ttm_pool_page_order_nodma() helper Matthew Brost
2026-11-05 11:27   ` Matthew Auld
2026-11-06  2:30   ` Niranjana Vishwanathapura
2026-07-11  2:55 ` [PATCH v3 03/33] drm/ttm: Record sub-optimal page order allocations in ttm_tt Matthew Brost
2026-11-06  2:34   ` Niranjana Vishwanathapura
2026-11-06 20:06     ` Matthew Brost
2026-07-11  2:55 ` [PATCH v3 04/33] drm/ttm: Introduce ttm_pool_alloc_iter for __ttm_pool_alloc() Matthew Brost
2026-11-06  2:39   ` Niranjana Vishwanathapura
2026-11-19 19:14     ` Matthew Brost
2026-07-11  2:55 ` [PATCH v3 05/33] drm/ttm: Support defragmentation moves Matthew Brost
2026-11-06  2:51   ` Niranjana Vishwanathapura
2026-11-19 20:15     ` Matthew Brost
2026-11-21  6:30       ` Niranjana Vishwanathapura [this message]
2026-07-11  2:55 ` [PATCH v3 06/33] drm/ttm: Add fault injection for beneficial-order allocation failures Matthew Brost
2026-11-06  2:54   ` Niranjana Vishwanathapura
2026-11-19 20:49     ` Matthew Brost
2026-07-11  2:55 ` [PATCH v3 07/33] drm/ttm: Harvest beneficial-order pages on defragmentation moves Matthew Brost
2026-11-10  2:37   ` Niranjana Vishwanathapura
2026-11-19 21:39     ` Matthew Brost
2026-11-20 23:09       ` Niranjana Vishwanathapura
2026-07-11  2:55 ` [PATCH v3 08/33] drm/ttm: Bound page (re)allocation per defragmentation move Matthew Brost
2026-11-10  2:44   ` Niranjana Vishwanathapura
2026-11-20  2:14     ` Matthew Brost
2026-11-20 20:37       ` Niranjana Vishwanathapura
2026-07-11  2:55 ` [PATCH v3 09/33] drm/ttm: Preallocate beneficial-order defrag pages outside the lock Matthew Brost
2026-11-11  0:29   ` Niranjana Vishwanathapura
2026-11-11  7:49   ` Niranjana Vishwanathapura
2026-11-20  2:29     ` Matthew Brost
2026-07-11  2:55 ` [PATCH v3 10/33] drm/ttm: Add full out-of-lock preallocation for ttm_pool_alloc() Matthew Brost
2026-11-11  7:31   ` Niranjana Vishwanathapura
2026-11-20  5:48     ` Matthew Brost
2026-11-21  5:03       ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 15/33] drm/xe: Track BOs backed at a sub-optimal page order Matthew Brost
2026-11-07  4:49   ` Niranjana Vishwanathapura
2026-11-20  6:02     ` Matthew Brost
2026-07-11  2:56 ` [PATCH v3 16/33] drm/xe: Back off beneficial-order reclaim under defrag pressure Matthew Brost
2026-11-07  5:02   ` Niranjana Vishwanathapura
2026-11-20  6:08     ` Matthew Brost
2026-07-11  2:56 ` [PATCH v3 17/33] drm/xe: Add xe_migrate_copy_defrag() for on-GPU defrag copies Matthew Brost
2026-11-03 12:58   ` Matthew Auld
2026-11-03 20:08     ` Matthew Brost
2026-11-04 12:37       ` Matthew Auld
2026-11-20  6:11         ` Matthew Brost
2026-11-07  5:07   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 18/33] drm/xe: Handle defrag moves in xe_bo_move() Matthew Brost
2026-11-07  5:12   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 19/33] drm/xe: Skip self-copies for borrowed pages on defrag moves Matthew Brost
2026-11-10  4:25   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 20/33] drm/xe: Add a page defragmentation worker Matthew Brost
2026-11-07  5:27   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 21/33] drm/xe: Add defrag GT stats Matthew Brost
2026-11-09  1:10   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 22/33] drm/xe: Add Kconfig.profile options for BO defrag configuration Matthew Brost
2026-11-09  1:31   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 23/33] drm/xe: Defrag using out-of-lock page preallocation Matthew Brost
2026-11-11  0:39   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 24/33] drm/xe: Add defrag profiling tracepoints Matthew Brost
2026-11-09  4:34   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 25/33] drm/xe: Preallocate system BO backing outside the dma-resv lock Matthew Brost
2026-11-11  7:36   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 26/33] drm/xe: Add tracepoint for xe_gem_create_ioctl Matthew Brost
2026-11-11  7:37   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 27/33] drm/xe: Add IOVA-based xe_res_cursor variant Matthew Brost
2026-11-04 12:23   ` Matthew Auld
2026-11-13  6:14   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 28/33] drm/xe: Use IOVA-based DMA mapping for eligible tt BOs Matthew Brost
2026-11-03 19:00   ` Matthew Auld
2026-11-03 20:21     ` Matthew Brost
2026-11-04 11:39       ` Matthew Auld
2026-11-05  3:04         ` Matthew Brost
2026-11-13  6:28   ` Niranjana Vishwanathapura
2026-11-13 20:09     ` Matthew Brost
2026-11-16  4:10       ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 29/33] drm/xe: Add per-device dependency scheduler for IOVA defrag finalize Matthew Brost
2026-11-14  1:47   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 30/33] drm/xe: Add packed copy-step IOVA mapping for defrag Matthew Brost
2026-11-14  1:52   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 31/33] drm/xe: Blit src-natural to dst-packed for defrag-IOVA copies Matthew Brost
2026-11-14  1:57   ` Niranjana Vishwanathapura
2026-11-16  0:41   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 32/33] drm/xe: Finalize defrag-IOVA moves with post-copy job Matthew Brost
2026-11-14  2:02   ` Niranjana Vishwanathapura
2026-07-11  2:56 ` [PATCH v3 33/33] drm/amdgpu: Preallocate system BO pages outside the reservation lock Matthew Brost
2026-07-11 10:46   ` Christian König
2026-07-13 20:24     ` Matthew Brost
2026-07-14  9:17       ` Christian König
2026-07-14 15:15         ` Matthew Brost
2026-11-16  1:01 ` [PATCH v3 00/33] drm/ttm, drm/xe: Minimize dma-resv hold times and defragment sub-optimally backed BOs Niranjana Vishwanathapura

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=awE6dk5EYBiu8k1-@nvishwa1-desk \
    --to=niranjana.vishwanathapura@intel.com \
    --cc=airlied@gmail.com \
    --cc=carlos.santa@intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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=ray.huang@amd.com \
    --cc=ryanneph@google.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --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

all inboxes | Powered by JetHome®